Triple

T21143633
Position Surface form Disambiguated ID Type / Status
Subject CNB E520993 entity
Predicate isOnRoute P2127 FINISHED
Object Kanpur–Lucknow 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: Kanpur–Lucknow section | Statement: [CNB, isOnRoute, Kanpur–Lucknow section]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Kanpur–Lucknow section
Context triple: [CNB, isOnRoute, Kanpur–Lucknow 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–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.
  • 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. 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.
  • E. Meerut–Muzaffarnagar–Saharanpur section
    The Meerut–Muzaffarnagar–Saharanpur section is a key railway corridor in northern India that connects major cities in western Uttar Pradesh and forms part of important regional and long-distance routes.
  • 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: Kanpur–Lucknow section
Target entity description: 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.
  • 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–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.
  • 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. 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.
  • E. Meerut–Muzaffarnagar–Saharanpur section
    The Meerut–Muzaffarnagar–Saharanpur section is a key railway corridor in northern India that connects major cities in western Uttar Pradesh and forms part of important regional and long-distance routes.
  • 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_69e0b50c6a848190a4e525a77a319b8a completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e723fbb29881909c4036eab46ed440 completed April 21, 2026, 7:15 a.m.
Created at: April 16, 2026, 2:57 p.m.