Triple

T18436568
Position Surface form Disambiguated ID Type / Status
Subject Delhi–Amritsar line E450406 entity
Predicate connectsTo P845 FINISHED
Object Delhi–Panipat 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: Delhi–Panipat section | Statement: [Delhi–Amritsar line, connectsTo, Delhi–Panipat section]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Delhi–Panipat section
Context triple: [Delhi–Amritsar line, connectsTo, Delhi–Panipat section]
  • A. 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.
  • B. 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.
  • C. Delhi–Agra section
    The Delhi–Agra section is a key railway corridor in northern India that connects the national capital, Delhi, with the historic city of Agra and forms part of a major passenger and tourist route.
  • D. Agra–Mathura section
    The Agra–Mathura section is a key railway line in northern India that connects the historic cities of Agra and Mathura and forms part of important regional and long-distance rail routes.
  • 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: Delhi–Panipat section
Target entity description: The Delhi–Panipat section is a key railway corridor in northern India that links the national capital Delhi with the industrial and historical city of Panipat, forming part of a major route toward Punjab.
  • A. 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.
  • B. 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.
  • C. Delhi–Agra section
    The Delhi–Agra section is a key railway corridor in northern India that connects the national capital, Delhi, with the historic city of Agra and forms part of a major passenger and tourist route.
  • D. Agra–Mathura section
    The Agra–Mathura section is a key railway line in northern India that connects the historic cities of Agra and Mathura and forms part of important regional and long-distance rail routes.
  • 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_69d8d381d6388190a9e94e9c658174e4 completed April 10, 2026, 10:40 a.m.
NER Named-entity recognition batch_69e51c0cd30c8190b8417c264e60d3a5 completed April 19, 2026, 6:16 p.m.
Created at: April 10, 2026, 11:29 a.m.