Triple
T5288105
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Central Railway zone |
E119673
|
entity |
| Predicate | majorRoute |
P385
|
FINISHED |
| Object |
New Delhi–Howrah trunk route (via Kanpur–Prayagraj)
The New Delhi–Howrah trunk route (via Kanpur–Prayagraj) is a key high-density railway corridor in India connecting the national capital with Kolkata through major northern and eastern cities.
|
E508045
|
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: New Delhi–Howrah trunk route (via Kanpur–Prayagraj) | Statement: [North Central Railway zone, majorRoute, New Delhi–Howrah trunk route (via Kanpur–Prayagraj)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: New Delhi–Howrah trunk route (via Kanpur–Prayagraj) Context triple: [North Central Railway zone, majorRoute, New Delhi–Howrah trunk route (via Kanpur–Prayagraj)]
-
A.
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.
-
B.
Howrah–Nagpur–Mumbai line
The Howrah–Nagpur–Mumbai line is a major Indian Railways trunk route connecting Kolkata (Howrah) in the east with Mumbai in the west via Nagpur, serving as a key corridor for both passenger and freight traffic across central India.
-
C.
Delhi–Moradabad–Bareilly–Lucknow line
The Delhi–Moradabad–Bareilly–Lucknow line is a key Indian Railways route in northern India that connects the national capital Delhi with major cities in Uttar Pradesh, including Moradabad, Bareilly, and the state capital Lucknow.
-
D.
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.
-
E.
Agra–Bandikui–Jaipur line
The Agra–Bandikui–Jaipur line is a key railway route in northern India that connects the historic city of Agra with Jaipur via Bandikui, 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.
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: New Delhi–Howrah trunk route (via Kanpur–Prayagraj) Triple: [North Central Railway zone, majorRoute, New Delhi–Howrah trunk route (via Kanpur–Prayagraj)]
Generated description
The New Delhi–Howrah trunk route (via Kanpur–Prayagraj) is a key high-density railway corridor in India connecting the national capital with Kolkata through major northern and eastern cities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: New Delhi–Howrah trunk route (via Kanpur–Prayagraj) Target entity description: The New Delhi–Howrah trunk route (via Kanpur–Prayagraj) is a key high-density railway corridor in India connecting the national capital with Kolkata through major northern and eastern cities.
-
A.
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.
-
B.
Howrah–Nagpur–Mumbai line
The Howrah–Nagpur–Mumbai line is a major Indian Railways trunk route connecting Kolkata (Howrah) in the east with Mumbai in the west via Nagpur, serving as a key corridor for both passenger and freight traffic across central India.
-
C.
Delhi–Moradabad–Bareilly–Lucknow line
The Delhi–Moradabad–Bareilly–Lucknow line is a key Indian Railways route in northern India that connects the national capital Delhi with major cities in Uttar Pradesh, including Moradabad, Bareilly, and the state capital Lucknow.
-
D.
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.
-
E.
Agra–Bandikui–Jaipur line
The Agra–Bandikui–Jaipur line is a key railway route in northern India that connects the historic city of Agra with Jaipur via Bandikui, serving as an important corridor for both passenger and freight traffic.
- 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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd84db300c8190a63ac51552f0e9a6 |
completed | March 20, 2026, 5:33 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bf06ecf4748190ab2bdd672f4ab14d |
completed | March 21, 2026, 9 p.m. |
| NEDg | Description generation | batch_69bf090aa7c88190a66694cec6d6a370 |
completed | March 21, 2026, 9:09 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69bf09d3b8148190b79bdf3cb77000b4 |
completed | March 21, 2026, 9:12 p.m. |
Created at: March 20, 2026, 1:52 p.m.