Triple
T17299631
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daund Junction |
E420006
|
entity |
| Predicate | locatedOnLine |
P2409
|
FINISHED |
| Object | Pune–Solapur 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: Pune–Solapur line | Statement: [Daund Junction, locatedOnLine, Pune–Solapur line]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Pune–Solapur line Context triple: [Daund Junction, locatedOnLine, Pune–Solapur line]
-
A.
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.
-
B.
Pune–Satara railway line
The Pune–Satara railway line is a key broad-gauge rail route in Maharashtra, India, connecting the city of Pune with Satara and serving as an important corridor for regional passenger and freight transport.
-
C.
Mumbai–Pune railway line
The Mumbai–Pune railway line is a major rail corridor in Maharashtra, India, connecting the metropolitan city of Mumbai with the industrial and educational hub of Pune through the Western Ghats.
-
D.
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.
-
E.
Mumbai–Nagpur line
The Mumbai–Nagpur line is a major Indian railway route connecting the western metropolis of Mumbai with the central city of Nagpur, serving as a key corridor for passenger and freight traffic across Maharashtra.
- 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: Pune–Solapur line Target entity description: 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.
-
A.
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.
-
B.
Pune–Satara railway line
The Pune–Satara railway line is a key broad-gauge rail route in Maharashtra, India, connecting the city of Pune with Satara and serving as an important corridor for regional passenger and freight transport.
-
C.
Mumbai–Pune railway line
The Mumbai–Pune railway line is a major rail corridor in Maharashtra, India, connecting the metropolitan city of Mumbai with the industrial and educational hub of Pune through the Western Ghats.
-
D.
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.
-
E.
Mumbai–Nagpur line
The Mumbai–Nagpur line is a major Indian railway route connecting the western metropolis of Mumbai with the central city of Nagpur, serving as a key corridor for passenger and freight traffic across Maharashtra.
- 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e438f8efb481908b56172c7f749b62 |
completed | April 19, 2026, 2:07 a.m. |
Created at: April 10, 2026, 5:41 a.m.