Triple
T19966683
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South East Central Railway zone |
E479952
|
entity |
| Predicate | hasRailCorridor |
P58937
|
FINISHED |
| Object | Raipur–Nagpur line segment |
—
|
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: Raipur–Nagpur line segment | Statement: [South East Central Railway zone, hasRailCorridor, Raipur–Nagpur line segment]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Raipur–Nagpur line segment Context triple: [South East Central Railway zone, hasRailCorridor, Raipur–Nagpur line segment]
-
A.
Nagpur–Bilaspur line
The Nagpur–Bilaspur line is a key railway route in central India that connects Nagpur in Maharashtra with Bilaspur in Chhattisgarh, forming part of an important east–west rail corridor.
-
B.
Jabalpur–Nainpur–Gondia line
The Jabalpur–Nainpur–Gondia line is a railway route in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, serving as an important regional link for passenger and freight traffic.
-
C.
Damoh–Katni line
The Damoh–Katni line is a railway route in the Indian state of Madhya Pradesh that connects the towns of Damoh and Katni as part of the regional rail network.
-
D.
Jabalpur–Nagpur section
The Jabalpur–Nagpur section is a key railway line in central India that connects the cities of Jabalpur in Madhya Pradesh and Nagpur in Maharashtra, serving as an important route for both passenger and freight trains.
-
E.
Nagpur–Itarsi line
The Nagpur–Itarsi line is a major railway route in central India that connects Nagpur in Maharashtra with Itarsi in Madhya Pradesh, serving as an important corridor for both passenger and freight traffic.
- 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: Raipur–Nagpur line segment Target entity description: The Raipur–Nagpur line segment is a key railway corridor in central India connecting Raipur in Chhattisgarh with Nagpur in Maharashtra, facilitating major passenger and freight movement across the region.
-
A.
Nagpur–Bilaspur line
The Nagpur–Bilaspur line is a key railway route in central India that connects Nagpur in Maharashtra with Bilaspur in Chhattisgarh, forming part of an important east–west rail corridor.
-
B.
Jabalpur–Nainpur–Gondia line
The Jabalpur–Nainpur–Gondia line is a railway route in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, serving as an important regional link for passenger and freight traffic.
-
C.
Damoh–Katni line
The Damoh–Katni line is a railway route in the Indian state of Madhya Pradesh that connects the towns of Damoh and Katni as part of the regional rail network.
-
D.
Jabalpur–Nagpur section
The Jabalpur–Nagpur section is a key railway line in central India that connects the cities of Jabalpur in Madhya Pradesh and Nagpur in Maharashtra, serving as an important route for both passenger and freight trains.
-
E.
Nagpur–Itarsi line
The Nagpur–Itarsi line is a major railway route in central India that connects Nagpur in Maharashtra with Itarsi in Madhya Pradesh, serving as an important corridor for both passenger and freight traffic.
- F. None of above. chosen
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_69d8e523c19881909f9197037200dde6 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65bc5e41881908c1e8867820f1c0c |
completed | April 20, 2026, 5 p.m. |
Created at: April 10, 2026, 1:54 p.m.