Triple
T18436569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delhi–Amritsar line |
E450406
|
entity |
| Predicate | connectsTo |
P845
|
FINISHED |
| Object | Ludhiana–Jalandhar 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: Ludhiana–Jalandhar section | Statement: [Delhi–Amritsar line, connectsTo, Ludhiana–Jalandhar section]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ludhiana–Jalandhar section Context triple: [Delhi–Amritsar line, connectsTo, Ludhiana–Jalandhar section]
-
A.
Jalandhar–Firozpur railway line
The Jalandhar–Firozpur railway line is a key rail route in the Indian state of Punjab that connects major cities in the Doaba and Malwa regions and supports both passenger and freight traffic.
-
B.
Amritsar–Pathankot line
The Amritsar–Pathankot line is a railway route in the Indian state of Punjab that connects the city of Amritsar with the border town of Pathankot, serving as an important regional and strategic rail corridor.
-
C.
Delhi–Panipat section
The Delhi–Panipat section is a key railway corridor in northern India that links the national capital Delhi with the industrial and historical city of Panipat, forming part of a major route toward Punjab.
-
D.
Delhi–Ambala railway line
The Delhi–Ambala railway line is a key rail corridor in northern India connecting the national capital Delhi with the city of Ambala, serving major towns and districts along its route.
-
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: Ludhiana–Jalandhar section Target entity description: The Ludhiana–Jalandhar section is a key railway corridor in the Indian state of Punjab that links the industrial city of Ludhiana with the major urban center of Jalandhar, forming part of an important route in northern India.
-
A.
Jalandhar–Firozpur railway line
The Jalandhar–Firozpur railway line is a key rail route in the Indian state of Punjab that connects major cities in the Doaba and Malwa regions and supports both passenger and freight traffic.
-
B.
Amritsar–Pathankot line
The Amritsar–Pathankot line is a railway route in the Indian state of Punjab that connects the city of Amritsar with the border town of Pathankot, serving as an important regional and strategic rail corridor.
-
C.
Delhi–Panipat section
The Delhi–Panipat section is a key railway corridor in northern India that links the national capital Delhi with the industrial and historical city of Panipat, forming part of a major route toward Punjab.
-
D.
Delhi–Ambala railway line
The Delhi–Ambala railway line is a key rail corridor in northern India connecting the national capital Delhi with the city of Ambala, serving major towns and districts along its route.
-
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
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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0cd30c8190b8417c264e60d3a5 |
completed | April 19, 2026, 6:16 p.m. |
Created at: April 10, 2026, 11:29 a.m.