Triple

T19886024
Position Surface form Disambiguated ID Type / Status
Subject Jabalpur railway division E477901 entity
Predicate hasRailwayLine P848 FINISHED
Object Jabalpur–Nainpur–Gondia 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: Jabalpur–Nainpur–Gondia line | Statement: [Jabalpur railway division, hasRailwayLine, Jabalpur–Nainpur–Gondia line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jabalpur–Nainpur–Gondia line
Context triple: [Jabalpur railway division, hasRailwayLine, Jabalpur–Nainpur–Gondia line]
  • A. 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.
  • B. 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.
  • C. 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.
  • D. Jhansi–Bina line
    The Jhansi–Bina line is a key railway route in central India that connects Jhansi in Uttar Pradesh with Bina in Madhya Pradesh, facilitating regional passenger and freight transport.
  • E. 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.
  • 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: Jabalpur–Nainpur–Gondia line
Target entity description: 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.
  • A. 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.
  • B. 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.
  • C. 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.
  • D. Jhansi–Bina line
    The Jhansi–Bina line is a key railway route in central India that connects Jhansi in Uttar Pradesh with Bina in Madhya Pradesh, facilitating regional passenger and freight transport.
  • E. 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.
  • 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_69d8e51f32b08190b3687f4f60353250 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65909fe0481908e22b60d04fe2b11 completed April 20, 2026, 4:49 p.m.
Created at: April 10, 2026, 1:52 p.m.