Triple
T17829966
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green Line (Chennai Metro) |
E445224
|
entity |
| Predicate | partOfNetwork |
P840
|
FINISHED |
| Object | Phase I of Chennai Metro |
—
|
NE NERFINISHED |
How this triple was built (3 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: Phase I of Chennai Metro | Statement: [Green Line (Chennai Metro), partOfNetwork, Phase I of Chennai Metro]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Phase I of Chennai Metro Context triple: [Green Line (Chennai Metro), partOfNetwork, Phase I of Chennai Metro]
-
A.
Chennai Metro
Chennai Metro is a rapid transit system serving the Indian city of Chennai, providing urban rail connectivity across key residential, commercial, and industrial areas.
-
B.
Chennai Central Metro
Chennai Central Metro is a major underground interchange station in Chennai, India, connecting the Chennai Metro network with the city’s primary railway terminus and other urban transit services.
-
C.
Chennai MRTS
Chennai MRTS is an elevated suburban railway network in Chennai, India, providing rapid transit services along key urban corridors and connecting with other city transport systems.
-
D.
Hyderabad Metro
Hyderabad Metro is a rapid transit system serving the city of Hyderabad, India, featuring multiple elevated corridors designed to ease urban traffic congestion and improve public transportation.
-
E.
Bangalore Metro
Bangalore Metro is a rapid transit system serving the city of Bengaluru, India, providing an elevated and underground rail network to ease urban transportation and reduce traffic congestion.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Phase I of Chennai Metro Target entity description: Phase I of Chennai Metro is the initial development stage of Chennai’s rapid transit system, comprising the first set of operational corridors and infrastructure built to introduce metro rail service to the city.
-
A.
Chennai Metro
chosen
Chennai Metro is a rapid transit system serving the Indian city of Chennai, providing urban rail connectivity across key residential, commercial, and industrial areas.
-
B.
Chennai Central Metro
Chennai Central Metro is a major underground interchange station in Chennai, India, connecting the Chennai Metro network with the city’s primary railway terminus and other urban transit services.
-
C.
Chennai MRTS
Chennai MRTS is an elevated suburban railway network in Chennai, India, providing rapid transit services along key urban corridors and connecting with other city transport systems.
-
D.
Hyderabad Metro
Hyderabad Metro is a rapid transit system serving the city of Hyderabad, India, featuring multiple elevated corridors designed to ease urban traffic congestion and improve public transportation.
-
E.
Bangalore Metro
Bangalore Metro is a rapid transit system serving the city of Bengaluru, India, providing an elevated and underground rail network to ease urban transportation and reduce traffic congestion.
- F. None of above.
Provenance (2 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_69d8b9f1a6d881909f024bc603111cdb |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48917c4d88190b919a4b75aed011c |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.