Triple
T22120066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nandgaon |
E546640
|
entity |
| Predicate | locatedOnRailwayLine |
P848
|
FINISHED |
| Object | Bhusawal–Manmad 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: Bhusawal–Manmad section | Statement: [Nandgaon, locatedOnRailwayLine, Bhusawal–Manmad section]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bhusawal–Manmad section Context triple: [Nandgaon, locatedOnRailwayLine, Bhusawal–Manmad section]
-
A.
Mumbai–Bhusawal section
The Mumbai–Bhusawal section is a major railway corridor in the Indian state of Maharashtra that connects Mumbai with Bhusawal and forms part of the busy trunk route of Indian Railways.
-
B.
Nagpur–Wardha section
The Nagpur–Wardha section is a key railway corridor in Maharashtra, India, connecting the major junctions of Nagpur and Wardha and forming part of important national rail routes.
-
C.
Pune–Manmad line
The Pune–Manmad line is a key railway route in the Indian state of Maharashtra that connects the city of Pune with Manmad, passing through important intermediate towns and junctions.
-
D.
Jabalpur–Bhusaval section
The Jabalpur–Bhusaval section is a key railway line in central India that connects Jabalpur in Madhya Pradesh with Bhusaval in Maharashtra, forming part of an important route for passenger and freight traffic.
-
E.
Bhopal–Nagpur section
The Bhopal–Nagpur section is a key railway corridor in central India that connects the cities of Bhopal and Nagpur, passing through important intermediate stations such as Betul.
- 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: Bhusawal–Manmad section Target entity description: The Bhusawal–Manmad section is a key railway corridor in Maharashtra, India, connecting the major junctions of Bhusawal and Manmad and serving as an important route for both passenger and freight trains.
-
A.
Mumbai–Bhusawal section
The Mumbai–Bhusawal section is a major railway corridor in the Indian state of Maharashtra that connects Mumbai with Bhusawal and forms part of the busy trunk route of Indian Railways.
-
B.
Nagpur–Wardha section
The Nagpur–Wardha section is a key railway corridor in Maharashtra, India, connecting the major junctions of Nagpur and Wardha and forming part of important national rail routes.
-
C.
Pune–Manmad line
The Pune–Manmad line is a key railway route in the Indian state of Maharashtra that connects the city of Pune with Manmad, passing through important intermediate towns and junctions.
-
D.
Jabalpur–Bhusaval section
The Jabalpur–Bhusaval section is a key railway line in central India that connects Jabalpur in Madhya Pradesh with Bhusaval in Maharashtra, forming part of an important route for passenger and freight traffic.
-
E.
Bhopal–Nagpur section
The Bhopal–Nagpur section is a key railway corridor in central India that connects the cities of Bhopal and Nagpur, passing through important intermediate stations such as Betul.
- 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_69e11e38b3848190ac3a4fa97d56e65a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12951fcd48190841319cd879c15cb |
completed | April 28, 2026, 9:40 p.m. |
Created at: April 16, 2026, 8:31 p.m.