Triple
T17397654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gorakhpur Junction railway station |
E422994
|
entity |
| Predicate | railwayLine |
P848
|
FINISHED |
| Object | Lucknow–Gorakhpur 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: Lucknow–Gorakhpur line | Statement: [Gorakhpur Junction railway station, railwayLine, Lucknow–Gorakhpur line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lucknow–Gorakhpur line Context triple: [Gorakhpur Junction railway station, railwayLine, Lucknow–Gorakhpur line]
-
A.
Kanpur–Jhansi line
The Kanpur–Jhansi line is a key railway route in northern India that connects the industrial city of Kanpur with Jhansi, facilitating major passenger and freight movement across Uttar Pradesh and beyond.
-
B.
Barauni–Gorakhpur line
The Barauni–Gorakhpur line is a key railway route in northern India that connects major junctions across Bihar and Uttar Pradesh, facilitating regional passenger and freight movement.
-
C.
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.
-
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.
Lucknow–Moradabad line
The Lucknow–Moradabad line is a key railway route in northern India connecting the cities of Lucknow and Moradabad and serving important intermediate junctions such as Bareilly.
- 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: Lucknow–Gorakhpur line Target entity description: The Lucknow–Gorakhpur line is a major railway route in the Indian state of Uttar Pradesh that connects the state capital Lucknow with the important rail hub of Gorakhpur, serving numerous intermediate towns and facilitating regional passenger and freight transport.
-
A.
Kanpur–Jhansi line
The Kanpur–Jhansi line is a key railway route in northern India that connects the industrial city of Kanpur with Jhansi, facilitating major passenger and freight movement across Uttar Pradesh and beyond.
-
B.
Barauni–Gorakhpur line
The Barauni–Gorakhpur line is a key railway route in northern India that connects major junctions across Bihar and Uttar Pradesh, facilitating regional passenger and freight movement.
-
C.
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.
-
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.
Lucknow–Moradabad line
The Lucknow–Moradabad line is a key railway route in northern India connecting the cities of Lucknow and Moradabad and serving important intermediate junctions such as Bareilly.
- 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_69d889d710288190bf0f4762801fefae |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43abe6f708190944aad636e1eb9a1 |
completed | April 19, 2026, 2:15 a.m. |
Created at: April 10, 2026, 5:45 a.m.