Triple
T19622712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | West Central Railway |
E471050
|
entity |
| Predicate | hasMajorRoute |
P385
|
FINISHED |
| Object | Kota–Nagda section |
—
|
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: Kota–Nagda section | Statement: [West Central Railway, hasMajorRoute, Kota–Nagda section]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Kota–Nagda section Context triple: [West Central Railway, hasMajorRoute, Kota–Nagda section]
-
A.
Agra–Tundla section
The Agra–Tundla section is a key railway line in northern India that connects the historic city of Agra with the junction town of Tundla, forming part of an important route on the Indian Railways network.
-
B.
Jabalpur–Itarsi section
The Jabalpur–Itarsi section is a key railway corridor in the Indian state of Madhya Pradesh that connects the city of Jabalpur with the major junction of Itarsi, serving numerous intermediate towns and facilitating regional passenger and freight movement.
-
C.
Agra–Mathura section
The Agra–Mathura section is a key railway line in northern India that connects the historic cities of Agra and Mathura and forms part of important regional and long-distance rail routes.
-
D.
Agra–Etawah section
The Agra–Etawah section is a key railway line in northern India that connects the historic city of Agra with Etawah, facilitating regional passenger and freight transport.
-
E.
Tatanagar–Bilaspur section
The Tatanagar–Bilaspur section is a key railway line in eastern India that connects Tatanagar (Jamshedpur) in Jharkhand with Bilaspur in Chhattisgarh, 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: Kota–Nagda section Target entity description: The Kota–Nagda section is a key railway line in India that connects Kota in Rajasthan with Nagda in Madhya Pradesh, serving as an important corridor for passenger and freight traffic.
-
A.
Agra–Tundla section
The Agra–Tundla section is a key railway line in northern India that connects the historic city of Agra with the junction town of Tundla, forming part of an important route on the Indian Railways network.
-
B.
Jabalpur–Itarsi section
The Jabalpur–Itarsi section is a key railway corridor in the Indian state of Madhya Pradesh that connects the city of Jabalpur with the major junction of Itarsi, serving numerous intermediate towns and facilitating regional passenger and freight movement.
-
C.
Agra–Mathura section
The Agra–Mathura section is a key railway line in northern India that connects the historic cities of Agra and Mathura and forms part of important regional and long-distance rail routes.
-
D.
Agra–Etawah section
The Agra–Etawah section is a key railway line in northern India that connects the historic city of Agra with Etawah, facilitating regional passenger and freight transport.
-
E.
Tatanagar–Bilaspur section
The Tatanagar–Bilaspur section is a key railway line in eastern India that connects Tatanagar (Jamshedpur) in Jharkhand with Bilaspur in Chhattisgarh, 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e7949081908a89414ef899fa20 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.