Triple
T19789681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Balaghat Junction railway station |
E475375
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Gondia–Balaghat railway 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: Gondia–Balaghat railway line | Statement: [Balaghat Junction railway station, locatedOn, Gondia–Balaghat railway line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gondia–Balaghat railway line Context triple: [Balaghat Junction railway station, locatedOn, Gondia–Balaghat railway line]
-
A.
Udhna–Jalgaon line
The Udhna–Jalgaon line is a railway route in western India that connects Udhna near Surat in Gujarat with Jalgaon in Maharashtra, serving as an important link for passenger and freight traffic in the region.
-
B.
Nagpur–Bilaspur line
The Nagpur–Bilaspur line is a key railway route in central India that connects Nagpur in Maharashtra with Bilaspur in Chhattisgarh, forming part of an important east–west rail corridor.
-
C.
Nagpur–Bhusawal line
The Nagpur–Bhusawal line is a major railway route in central India that connects Nagpur with Bhusawal, forming an important segment of the Howrah–Mumbai main line.
-
D.
Vadodara–Chhota Udepur line
The Vadodara–Chhota Udepur line is a railway route in the Indian state of Gujarat that connects the major junction city of Vadodara with the town of Chhota Udepur, serving regional passenger and freight traffic.
-
E.
Nagpur–Itarsi line
The Nagpur–Itarsi line is a major railway route in central India that connects Nagpur in Maharashtra with Itarsi in Madhya Pradesh, serving as an important corridor 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: Gondia–Balaghat railway line Target entity description: The Gondia–Balaghat railway line is a regional rail route in central India that connects the towns of Gondia and Balaghat, serving as an important link in the area’s passenger and freight transport network.
-
A.
Udhna–Jalgaon line
The Udhna–Jalgaon line is a railway route in western India that connects Udhna near Surat in Gujarat with Jalgaon in Maharashtra, serving as an important link for passenger and freight traffic in the region.
-
B.
Nagpur–Bilaspur line
The Nagpur–Bilaspur line is a key railway route in central India that connects Nagpur in Maharashtra with Bilaspur in Chhattisgarh, forming part of an important east–west rail corridor.
-
C.
Nagpur–Bhusawal line
The Nagpur–Bhusawal line is a major railway route in central India that connects Nagpur with Bhusawal, forming an important segment of the Howrah–Mumbai main line.
-
D.
Vadodara–Chhota Udepur line
The Vadodara–Chhota Udepur line is a railway route in the Indian state of Gujarat that connects the major junction city of Vadodara with the town of Chhota Udepur, serving regional passenger and freight traffic.
-
E.
Nagpur–Itarsi line
The Nagpur–Itarsi line is a major railway route in central India that connects Nagpur in Maharashtra with Itarsi in Madhya Pradesh, serving as an important corridor 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_69d8e51b014081908b263e167370529a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6538ae5108190b80eb7de6f445f02 |
completed | April 20, 2026, 4:25 p.m. |
Created at: April 10, 2026, 1:49 p.m.