Triple
T22120032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manmad |
E546639
|
entity |
| Predicate | locatedOnRailwayLine |
P848
|
FINISHED |
| Object | Manmad–Aurangabad–Nanded 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: Manmad–Aurangabad–Nanded line | Statement: [Manmad, locatedOnRailwayLine, Manmad–Aurangabad–Nanded line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Manmad–Aurangabad–Nanded line Context triple: [Manmad, locatedOnRailwayLine, Manmad–Aurangabad–Nanded line]
-
A.
Mumbai–Bhusawal–Itarsi line
The Mumbai–Bhusawal–Itarsi line is a major Indian railway corridor connecting Mumbai with central and northern India via Bhusawal and Itarsi, carrying significant passenger and freight traffic.
-
B.
Pune–Solapur line
The Pune–Solapur line is a key railway route in the Indian state of Maharashtra that connects the major cities of Pune and Solapur and serves as an important corridor for both passenger and freight traffic.
-
C.
Pune–Miraj–Londa line
The Pune–Miraj–Londa line is a key railway route in western and southern India that connects Maharashtra with Karnataka, serving as an important corridor for both passenger and freight traffic.
-
D.
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.
-
E.
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.
- 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: Manmad–Aurangabad–Nanded line Target entity description: The Manmad–Aurangabad–Nanded line is a railway route in the Indian state of Maharashtra that connects the junction town of Manmad with the cities of Aurangabad and Nanded, serving as an important regional transport corridor.
-
A.
Mumbai–Bhusawal–Itarsi line
The Mumbai–Bhusawal–Itarsi line is a major Indian railway corridor connecting Mumbai with central and northern India via Bhusawal and Itarsi, carrying significant passenger and freight traffic.
-
B.
Pune–Solapur line
The Pune–Solapur line is a key railway route in the Indian state of Maharashtra that connects the major cities of Pune and Solapur and serves as an important corridor for both passenger and freight traffic.
-
C.
Pune–Miraj–Londa line
The Pune–Miraj–Londa line is a key railway route in western and southern India that connects Maharashtra with Karnataka, serving as an important corridor for both passenger and freight traffic.
-
D.
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.
-
E.
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.
- 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.