Triple

T18860960
Position Surface form Disambiguated ID Type / Status
Subject Shatabdi Express E461308 entity
Predicate firstRoute P6298 FINISHED
Object New Delhi–Jhansi 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: New Delhi–Jhansi | Statement: [Shatabdi Express, firstRoute, New Delhi–Jhansi]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: New Delhi–Jhansi
Context triple: [Shatabdi Express, firstRoute, New Delhi–Jhansi]
  • A. Varanasi–Jaunpur line
    The Varanasi–Jaunpur line is a railway route in the Indian state of Uttar Pradesh that connects the historic city of Varanasi with Jaunpur, serving as an important regional passenger and freight corridor.
  • B. Agra–Gwalior–Jhansi line
    The Agra–Gwalior–Jhansi line is a key railway route in northern India that connects the historic cities of Agra, Gwalior, and Jhansi, serving as an important corridor for both passenger and freight traffic.
  • C. 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.
  • D. Varanasi–Lucknow line
    The Varanasi–Lucknow line is a key railway route in the Indian state of Uttar Pradesh that connects the major cities of Varanasi and Lucknow, serving as an important corridor for both passenger and freight traffic.
  • E. Delhi–Moradabad line
    The Delhi–Moradabad line is a major railway route in northern India that connects the national capital region with the city of Moradabad and forms part of important passenger and freight corridors.
  • 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: New Delhi–Jhansi
Target entity description: New Delhi–Jhansi is a major intercity rail corridor in northern India connecting the national capital with the historic city of Jhansi in Uttar Pradesh.
  • A. Varanasi–Jaunpur line
    The Varanasi–Jaunpur line is a railway route in the Indian state of Uttar Pradesh that connects the historic city of Varanasi with Jaunpur, serving as an important regional passenger and freight corridor.
  • B. Agra–Gwalior–Jhansi line
    The Agra–Gwalior–Jhansi line is a key railway route in northern India that connects the historic cities of Agra, Gwalior, and Jhansi, serving as an important corridor for both passenger and freight traffic.
  • C. 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.
  • D. Varanasi–Lucknow line
    The Varanasi–Lucknow line is a key railway route in the Indian state of Uttar Pradesh that connects the major cities of Varanasi and Lucknow, serving as an important corridor for both passenger and freight traffic.
  • E. Delhi–Moradabad line
    The Delhi–Moradabad line is a major railway route in northern India that connects the national capital region with the city of Moradabad and forms part of important passenger and freight corridors.
  • 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_69d8dcfb7b9c8190854e7b171b98ea2e completed April 10, 2026, 11:20 a.m.
NER Named-entity recognition batch_69e5c060bfc4819092ac591692a6ccd5 completed April 20, 2026, 5:57 a.m.
Created at: April 10, 2026, 11:57 a.m.