Triple
T21261018
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kanpur–Mathura line |
E524000
|
entity |
| Predicate | partOfCorridor |
P840
|
FINISHED |
| Object | Delhi–Howrah route via Kanpur |
—
|
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: Delhi–Howrah route via Kanpur | Statement: [Kanpur–Mathura line, partOfCorridor, Delhi–Howrah route via Kanpur]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Delhi–Howrah route via Kanpur Context triple: [Kanpur–Mathura line, partOfCorridor, Delhi–Howrah route via Kanpur]
-
A.
Varanasi–Lucknow line
The Varanasi–Lucknow line is a key railway route in the Indian state of Uttar Pradesh that connects the major cities of Varanasi and Lucknow, serving as an important corridor for both passenger and freight traffic.
-
B.
Howrah–Prayagraj–Mumbai line
The Howrah–Prayagraj–Mumbai line is a major Indian Railways trunk route connecting Kolkata (Howrah) in the east with Mumbai in the west via Prayagraj, passing through key junctions across northern and central India.
-
C.
New Delhi–Jhansi
New Delhi–Jhansi is a major intercity rail corridor in northern India connecting the national capital with the historic city of Jhansi in Uttar Pradesh.
-
D.
Varanasi–Jaunpur line
The Varanasi–Jaunpur line is a railway route in the Indian state of Uttar Pradesh that connects the historic city of Varanasi with Jaunpur, serving as an important regional passenger and freight corridor.
-
E.
Delhi–Kanpur section
The Delhi–Kanpur section is a major railway corridor in northern India that connects the national capital Delhi with the industrial city of Kanpur, carrying heavy 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: Delhi–Howrah route via Kanpur Target entity description: The Delhi–Howrah route via Kanpur is a major Indian Railways trunk corridor connecting the national capital Delhi with Kolkata (Howrah) through Kanpur, forming one of the busiest and most important passenger and freight routes in the country.
-
A.
Varanasi–Lucknow line
The Varanasi–Lucknow line is a key railway route in the Indian state of Uttar Pradesh that connects the major cities of Varanasi and Lucknow, serving as an important corridor for both passenger and freight traffic.
-
B.
Howrah–Prayagraj–Mumbai line
The Howrah–Prayagraj–Mumbai line is a major Indian Railways trunk route connecting Kolkata (Howrah) in the east with Mumbai in the west via Prayagraj, passing through key junctions across northern and central India.
-
C.
New Delhi–Jhansi
New Delhi–Jhansi is a major intercity rail corridor in northern India connecting the national capital with the historic city of Jhansi in Uttar Pradesh.
-
D.
Varanasi–Jaunpur line
The Varanasi–Jaunpur line is a railway route in the Indian state of Uttar Pradesh that connects the historic city of Varanasi with Jaunpur, serving as an important regional passenger and freight corridor.
-
E.
Delhi–Kanpur section
chosen
The Delhi–Kanpur section is a major railway corridor in northern India that connects the national capital Delhi with the industrial city of Kanpur, carrying heavy passenger and freight traffic.
- 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_69e0b5156d7881909bd4f83676590715 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e735e6a0448190ad412a8fcbbd8ff0 |
completed | April 21, 2026, 8:31 a.m. |
Created at: April 16, 2026, 3:59 p.m.