Triple
T11840525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoshangabad railway station |
E281637
|
entity |
| Predicate | isOnRoute |
P2127
|
FINISHED |
| Object |
Delhi–Bhopal–Itarsi–Nagpur–Chennai route
The Delhi–Bhopal–Itarsi–Nagpur–Chennai route is a major Indian Railways trunk line connecting the national capital in the north to the southern metropolis of Chennai via key central Indian cities.
|
E950516
|
NE FINISHED |
How this triple was built (4 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: Delhi–Bhopal–Itarsi–Nagpur–Chennai route | Statement: [Hoshangabad railway station, isOnRoute, Delhi–Bhopal–Itarsi–Nagpur–Chennai route]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Delhi–Bhopal–Itarsi–Nagpur–Chennai route Context triple: [Hoshangabad railway station, isOnRoute, Delhi–Bhopal–Itarsi–Nagpur–Chennai route]
-
A.
Jabalpur–Nainpur–Gondia route
The Jabalpur–Nainpur–Gondia route is a railway line in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, passing through the important junction town of Nainpur.
-
B.
Nagpur–Wardha–Badnera route
The Nagpur–Wardha–Badnera route is a key railway corridor in Maharashtra, India, connecting major junctions in the Vidarbha region and forming part of an important trunk line for passenger and freight traffic.
-
C.
Delhi–Mumbai (via Ratlam) trunk route
The Delhi–Mumbai (via Ratlam) trunk route is a major Indian Railways corridor connecting the national capital with the financial capital through central-western India, carrying heavy passenger and freight traffic.
-
D.
Mumbai–Pune route
The Mumbai–Pune route is a major transport corridor in western India connecting the cities of Mumbai and Pune, known for passing through the scenic hill station region of Lonavala.
-
E.
Mumbai–Ahmedabad route
The Mumbai–Ahmedabad route is a major rail and transport corridor in western India connecting the metropolitan cities of Mumbai and Ahmedabad.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Delhi–Bhopal–Itarsi–Nagpur–Chennai route Triple: [Hoshangabad railway station, isOnRoute, Delhi–Bhopal–Itarsi–Nagpur–Chennai route]
Generated description
The Delhi–Bhopal–Itarsi–Nagpur–Chennai route is a major Indian Railways trunk line connecting the national capital in the north to the southern metropolis of Chennai via key central Indian cities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Delhi–Bhopal–Itarsi–Nagpur–Chennai route Target entity description: The Delhi–Bhopal–Itarsi–Nagpur–Chennai route is a major Indian Railways trunk line connecting the national capital in the north to the southern metropolis of Chennai via key central Indian cities.
-
A.
Jabalpur–Nainpur–Gondia route
The Jabalpur–Nainpur–Gondia route is a railway line in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, passing through the important junction town of Nainpur.
-
B.
Nagpur–Wardha–Badnera route
The Nagpur–Wardha–Badnera route is a key railway corridor in Maharashtra, India, connecting major junctions in the Vidarbha region and forming part of an important trunk line for passenger and freight traffic.
-
C.
Delhi–Mumbai (via Ratlam) trunk route
The Delhi–Mumbai (via Ratlam) trunk route is a major Indian Railways corridor connecting the national capital with the financial capital through central-western India, carrying heavy passenger and freight traffic.
-
D.
Mumbai–Pune route
The Mumbai–Pune route is a major transport corridor in western India connecting the cities of Mumbai and Pune, known for passing through the scenic hill station region of Lonavala.
-
E.
Mumbai–Ahmedabad route
The Mumbai–Ahmedabad route is a major rail and transport corridor in western India connecting the metropolitan cities of Mumbai and Ahmedabad.
- F. None of above. chosen
Provenance (5 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_69d6ab276f8c8190b1966a0ef11349ac |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d8a658f918819092c2db05fe2ab0ce |
completed | April 10, 2026, 7:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f1678668ac81909bddf67e8c176757 |
completed | April 29, 2026, 2:05 a.m. |
| NEDg | Description generation | batch_69f17004fb908190a486c6718c5252cb |
completed | April 29, 2026, 2:42 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f1db11f0f48190832ca4f552f21751 |
completed | April 29, 2026, 10:18 a.m. |
Created at: April 8, 2026, 9:43 p.m.