Triple
T18959728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tarn Taran Junction |
E463879
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Amritsar–Khem Karan line |
—
|
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: Amritsar–Khem Karan line | Statement: [Tarn Taran Junction, railwayLine, Amritsar–Khem Karan line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Amritsar–Khem Karan line Context triple: [Tarn Taran Junction, railwayLine, Amritsar–Khem Karan line]
-
A.
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.
-
B.
Delhi–Amritsar line
The Delhi–Amritsar line is a major Indian Railways route connecting the national capital Delhi with the city of Amritsar in Punjab, serving as a key passenger and freight corridor in North India.
-
C.
Jammu–Pathankot line
The Jammu–Pathankot line is a key railway route in northern India that connects the plains of Punjab with the Jammu region, serving as a vital link for both passenger and strategic military transport.
-
D.
Ambala–Attari line
The Ambala–Attari line is a major railway route in northern India that connects Ambala in Haryana to Attari near the India–Pakistan border, serving as an important corridor for both passenger and freight traffic.
-
E.
Bikaner–Sri Ganganagar line
The Bikaner–Sri Ganganagar line is a railway route in the Indian state of Rajasthan that connects the city of Bikaner with Sri Ganganagar, serving as an important regional transport corridor.
- 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: Amritsar–Khem Karan line Target entity description: The Amritsar–Khem Karan line is a railway route in the Indian state of Punjab that connects the city of Amritsar to the border town of Khem Karan, serving several intermediate junctions and local communities.
-
A.
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.
-
B.
Delhi–Amritsar line
The Delhi–Amritsar line is a major Indian Railways route connecting the national capital Delhi with the city of Amritsar in Punjab, serving as a key passenger and freight corridor in North India.
-
C.
Jammu–Pathankot line
The Jammu–Pathankot line is a key railway route in northern India that connects the plains of Punjab with the Jammu region, serving as a vital link for both passenger and strategic military transport.
-
D.
Ambala–Attari line
The Ambala–Attari line is a major railway route in northern India that connects Ambala in Haryana to Attari near the India–Pakistan border, serving as an important corridor for both passenger and freight traffic.
-
E.
Bikaner–Sri Ganganagar line
The Bikaner–Sri Ganganagar line is a railway route in the Indian state of Rajasthan that connects the city of Bikaner with Sri Ganganagar, serving as an important regional transport corridor.
- 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_69d8dcffc278819086792a4ebfddfafa |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d5d1d784819095f3f886d7c47175 |
completed | April 20, 2026, 7:29 a.m. |
Created at: April 10, 2026, noon