Triple

T19363179
Position Surface form Disambiguated ID Type / Status
Subject Mainpuri E484330 entity
Predicate railwayLine P848 FINISHED
Object Shikohabad–Mainpuri 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: Shikohabad–Mainpuri line | Statement: [Mainpuri, railwayLine, Shikohabad–Mainpuri line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Shikohabad–Mainpuri line
Context triple: [Mainpuri, railwayLine, Shikohabad–Mainpuri line]
  • A. Kanpur–Jhansi line
    The Kanpur–Jhansi line is a key railway route in northern India that connects the industrial city of Kanpur with Jhansi, facilitating major passenger and freight movement across Uttar Pradesh and beyond.
  • B. Lucknow–Bahraich line
    The Lucknow–Bahraich line is a railway route in the Indian state of Uttar Pradesh that connects the city of Lucknow with Bahraich, serving as an important regional passenger and freight corridor.
  • C. Gorakhpur–Nautanwa line
    The Gorakhpur–Nautanwa line is a railway route in the Indian state of Uttar Pradesh that connects the major rail hub of Gorakhpur with the town of Nautanwa near the Nepal border.
  • D. Samastipur–Muzaffarpur line
    The Samastipur–Muzaffarpur line is a key railway route in the Indian state of Bihar that connects the important regional centers of Samastipur and Muzaffarpur within the East Central Railway zone.
  • E. Lucknow–Gorakhpur line
    The Lucknow–Gorakhpur line is a major railway route in the Indian state of Uttar Pradesh that connects the state capital Lucknow with the important rail hub of Gorakhpur, serving numerous intermediate towns and facilitating regional passenger and freight transport.
  • 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: Shikohabad–Mainpuri line
Target entity description: The Shikohabad–Mainpuri line is a regional railway route in Uttar Pradesh, India, connecting the towns of Shikohabad and Mainpuri within the North Central Railway zone.
  • A. Kanpur–Jhansi line
    The Kanpur–Jhansi line is a key railway route in northern India that connects the industrial city of Kanpur with Jhansi, facilitating major passenger and freight movement across Uttar Pradesh and beyond.
  • B. Lucknow–Bahraich line
    The Lucknow–Bahraich line is a railway route in the Indian state of Uttar Pradesh that connects the city of Lucknow with Bahraich, serving as an important regional passenger and freight corridor.
  • C. Gorakhpur–Nautanwa line
    The Gorakhpur–Nautanwa line is a railway route in the Indian state of Uttar Pradesh that connects the major rail hub of Gorakhpur with the town of Nautanwa near the Nepal border.
  • D. Samastipur–Muzaffarpur line
    The Samastipur–Muzaffarpur line is a key railway route in the Indian state of Bihar that connects the important regional centers of Samastipur and Muzaffarpur within the East Central Railway zone.
  • E. Lucknow–Gorakhpur line
    The Lucknow–Gorakhpur line is a major railway route in the Indian state of Uttar Pradesh that connects the state capital Lucknow with the important rail hub of Gorakhpur, serving numerous intermediate towns and facilitating regional passenger and freight transport.
  • 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_69d8e8d305088190ad13571532aa454c completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e619a897008190a2c62a50ca60de2d completed April 20, 2026, 12:18 p.m.
Created at: April 10, 2026, 1:34 p.m.