Triple
T19949096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ludhiana Junction railway station |
E479507
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Ludhiana–Fazilka 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: Ludhiana–Fazilka line | Statement: [Ludhiana Junction railway station, locatedOn, Ludhiana–Fazilka line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ludhiana–Fazilka line Context triple: [Ludhiana Junction railway station, locatedOn, Ludhiana–Fazilka line]
-
A.
Firozpur–Bathinda line
The Firozpur–Bathinda line is a railway route in the Indian state of Punjab that connects the city of Firozpur with Bathinda, serving as an important regional transport corridor.
-
B.
Delhi–Fazilka line
The Delhi–Fazilka line is a key broad-gauge railway route in northern India that connects the national capital Delhi with the border region near Fazilka in Punjab, serving numerous intermediate cities and military cantonments.
-
C.
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.
-
D.
Amritsar–Khem Karan line
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.
-
E.
Jalandhar–Jammu Tawi line
The Jalandhar–Jammu Tawi line is a key broad-gauge railway route in northern India that connects Punjab with Jammu and Kashmir, serving as an important link for both 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–Fazilka line Target entity description: The Ludhiana–Fazilka line is a railway route in the Indian state of Punjab that connects the industrial city of Ludhiana with the border town of Fazilka, serving as an important regional transport corridor.
-
A.
Firozpur–Bathinda line
The Firozpur–Bathinda line is a railway route in the Indian state of Punjab that connects the city of Firozpur with Bathinda, serving as an important regional transport corridor.
-
B.
Delhi–Fazilka line
The Delhi–Fazilka line is a key broad-gauge railway route in northern India that connects the national capital Delhi with the border region near Fazilka in Punjab, serving numerous intermediate cities and military cantonments.
-
C.
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.
-
D.
Amritsar–Khem Karan line
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.
-
E.
Jalandhar–Jammu Tawi line
The Jalandhar–Jammu Tawi line is a key broad-gauge railway route in northern India that connects Punjab with Jammu and Kashmir, serving as an important link for both 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a69ae388190918e862012f9fe39 |
completed | April 20, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:54 p.m.