Triple
T27931548
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Navi Mumbai Municipal Transport |
E707994
|
entity |
| Predicate | operatorFor |
P179
|
FINISHED |
| Object | Navi Mumbai city |
E352594
|
NE FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Navi Mumbai city | Statement: [Navi Mumbai Municipal Transport, operatorFor, Navi Mumbai city]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: operatorFor Context triple: [Navi Mumbai Municipal Transport, operatorFor, Navi Mumbai city]
-
A.
operatorUse
Indicates that an operator or tool is being used or applied by one entity to act upon or interact with another entity.
-
B.
operatorBase
Indicates that one entity serves as the primary or foundational operator for another entity or operation.
-
C.
operator
chosen
Indicates that one entity functions as the operator (controller or handler) of another entity, such as a system, device, or process.
-
D.
operatorVariant
Indicates a relationship where one operator is an alternative or modified form of another, typically differing in implementation, configuration, or usage while serving a related function.
-
E.
operatorSymbol
Indicates the symbolic notation used to represent an operator in an expression or formal system.
- F. None of above.
Provenance (4 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69ef96bbf2c48190a9d0e0291457aab6 |
completed | April 27, 2026, 5:02 p.m. |
| NER | Named-entity recognition | batch_69fe5d58c3e48190910aa3c23485e2c4 |
completed | May 8, 2026, 10:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a15e68e20b081908484dff44e122fbb |
completed | May 26, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69fe5c92090c8190bcfa412c0a3619df |
completed | May 8, 2026, 9:58 p.m. |
Created at: April 27, 2026, 7:03 p.m.