Triple

T20353577
Position Surface form Disambiguated ID Type / Status
Subject Chhindwara Junction E496082 entity
Predicate hasRailwayLine P848 FINISHED
Object Chhindwara–Nagpur 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: Chhindwara–Nagpur line | Statement: [Chhindwara Junction, hasRailwayLine, Chhindwara–Nagpur line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Chhindwara–Nagpur line
Context triple: [Chhindwara Junction, hasRailwayLine, Chhindwara–Nagpur line]
  • A. 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.
  • B. Jabalpur–Nainpur–Gondia line
    The Jabalpur–Nainpur–Gondia line is a railway route in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, serving as an important regional link for passenger and freight traffic.
  • C. Jabalpur–Katni line
    The Jabalpur–Katni line is a key railway route in the Indian state of Madhya Pradesh that connects the cities of Jabalpur and Katni, facilitating regional passenger and freight transport.
  • D. Purna–Khandwa line
    The Purna–Khandwa line is a railway route in central India that connects Purna in Maharashtra to Khandwa in Madhya Pradesh, serving as an important regional link for passenger and freight traffic.
  • E. Jabalpur–Itarsi line
    The Jabalpur–Itarsi line is a key railway route in the Indian state of Madhya Pradesh that connects the city of Jabalpur with the major junction of Itarsi, facilitating regional and long-distance rail 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: Chhindwara–Nagpur line
Target entity description: The Chhindwara–Nagpur line is a railway route in central India that connects the town of Chhindwara in Madhya Pradesh with the city of Nagpur in Maharashtra, serving as an important regional transport link.
  • A. 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.
  • B. Jabalpur–Nainpur–Gondia line
    The Jabalpur–Nainpur–Gondia line is a railway route in central India that connects Jabalpur in Madhya Pradesh with Gondia in Maharashtra, serving as an important regional link for passenger and freight traffic.
  • C. Jabalpur–Katni line
    The Jabalpur–Katni line is a key railway route in the Indian state of Madhya Pradesh that connects the cities of Jabalpur and Katni, facilitating regional passenger and freight transport.
  • D. Purna–Khandwa line
    The Purna–Khandwa line is a railway route in central India that connects Purna in Maharashtra to Khandwa in Madhya Pradesh, serving as an important regional link for passenger and freight traffic.
  • E. Jabalpur–Itarsi line
    The Jabalpur–Itarsi line is a key railway route in the Indian state of Madhya Pradesh that connects the city of Jabalpur with the major junction of Itarsi, facilitating regional and long-distance rail 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_69e0b4a3f7f48190b37f354574028ca6 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e67851c7088190ba960a33c6dfa824 completed April 20, 2026, 7:02 p.m.
Created at: April 16, 2026, 11:25 a.m.