Triple

T22340942
Position Surface form Disambiguated ID Type / Status
Subject Mughalsarai Junction railway station E552271 entity
Predicate line P1293 FINISHED
Object Mughalsarai–Kanpur section — 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: Mughalsarai–Kanpur section | Statement: [Mughalsarai Junction railway station, line, Mughalsarai–Kanpur section]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Mughalsarai–Kanpur section
Context triple: [Mughalsarai Junction railway station, line, Mughalsarai–Kanpur section]
  • A. Agra–Kanpur section
    The Agra–Kanpur section is a key railway corridor in the Indian state of Uttar Pradesh that connects the major cities of Agra and Kanpur and forms part of the broader rail network linking northern India.
  • B. Kanpur–Lucknow section
    The Kanpur–Lucknow section is a key railway corridor in the Indian state of Uttar Pradesh that connects the major cities of Kanpur and Lucknow and forms part of the busy Delhi–Howrah route.
  • C. Delhi–Kanpur section
    The Delhi–Kanpur section is a major railway corridor in northern India that connects the national capital Delhi with the industrial city of Kanpur, carrying heavy passenger and freight traffic.
  • D. Kanpur–Prayagraj section
    The Kanpur–Prayagraj section is a key railway line in the Indian state of Uttar Pradesh that connects the major cities of Kanpur and Prayagraj and forms part of important national rail corridors.
  • E. Agra–Etawah section
    The Agra–Etawah section is a key railway line in northern India that connects the historic city of Agra with Etawah, 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: Mughalsarai–Kanpur section
Target entity description: The Mughalsarai–Kanpur section is a major railway corridor in northern India that forms part of the busy Delhi–Howrah route, carrying heavy passenger and freight traffic across Uttar Pradesh.
  • A. Agra–Kanpur section
    The Agra–Kanpur section is a key railway corridor in the Indian state of Uttar Pradesh that connects the major cities of Agra and Kanpur and forms part of the broader rail network linking northern India.
  • B. Kanpur–Lucknow section
    The Kanpur–Lucknow section is a key railway corridor in the Indian state of Uttar Pradesh that connects the major cities of Kanpur and Lucknow and forms part of the busy Delhi–Howrah route.
  • C. Delhi–Kanpur section
    The Delhi–Kanpur section is a major railway corridor in northern India that connects the national capital Delhi with the industrial city of Kanpur, carrying heavy passenger and freight traffic.
  • D. Kanpur–Prayagraj section
    The Kanpur–Prayagraj section is a key railway line in the Indian state of Uttar Pradesh that connects the major cities of Kanpur and Prayagraj and forms part of important national rail corridors.
  • E. Agra–Etawah section
    The Agra–Etawah section is a key railway line in northern India that connects the historic city of Agra with Etawah, 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_69e11e494eec81909c4d2d51f69499d9 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15783637c8190b77885f4e23d7ee5 completed April 29, 2026, 12:57 a.m.
Created at: April 16, 2026, 8:43 p.m.