Triple

T19821823
Position Surface form Disambiguated ID Type / Status
Subject Sabarmati railway station E476212 entity
Predicate hasLine P35 FINISHED
Object Ahmedabad–Mehsana 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: Ahmedabad–Mehsana line | Statement: [Sabarmati railway station, hasLine, Ahmedabad–Mehsana line]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Ahmedabad–Mehsana line
Context triple: [Sabarmati railway station, hasLine, Ahmedabad–Mehsana line]
  • A. Ahmedabad–Rajkot line
    The Ahmedabad–Rajkot line is a key railway route in the Indian state of Gujarat that connects the major cities of Ahmedabad and Rajkot, facilitating both passenger and freight transport.
  • B. Ahmedabad–Vadodara line
    The Ahmedabad–Vadodara line is a key railway corridor in the Indian state of Gujarat that connects the major cities of Ahmedabad and Vadodara and forms part of the busy Western Railway network.
  • C. Ahmedabad–Gandhinagar line
    The Ahmedabad–Gandhinagar line is a railway route in the Indian state of Gujarat that connects the major city of Ahmedabad with the state capital, Gandhinagar.
  • D. Ahmedabad–Udaipur line
    The Ahmedabad–Udaipur line is a railway route in western India that connects the city of Ahmedabad in Gujarat with Udaipur in Rajasthan, serving as an important regional passenger and freight corridor.
  • E. Ahmedabad–Bhavnagar line
    The Ahmedabad–Bhavnagar line is a railway route in the Indian state of Gujarat that connects the major city of Ahmedabad with the coastal city of Bhavnagar, serving as an important regional transport corridor.
  • 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: Ahmedabad–Mehsana line
Target entity description: The Ahmedabad–Mehsana line is a key railway route in the Indian state of Gujarat that connects the city of Ahmedabad with the town of Mehsana, serving as an important regional transport corridor.
  • A. Ahmedabad–Rajkot line
    The Ahmedabad–Rajkot line is a key railway route in the Indian state of Gujarat that connects the major cities of Ahmedabad and Rajkot, facilitating both passenger and freight transport.
  • B. Ahmedabad–Vadodara line
    The Ahmedabad–Vadodara line is a key railway corridor in the Indian state of Gujarat that connects the major cities of Ahmedabad and Vadodara and forms part of the busy Western Railway network.
  • C. Ahmedabad–Gandhinagar line
    The Ahmedabad–Gandhinagar line is a railway route in the Indian state of Gujarat that connects the major city of Ahmedabad with the state capital, Gandhinagar.
  • D. Ahmedabad–Udaipur line
    The Ahmedabad–Udaipur line is a railway route in western India that connects the city of Ahmedabad in Gujarat with Udaipur in Rajasthan, serving as an important regional passenger and freight corridor.
  • E. Ahmedabad–Bhavnagar line
    The Ahmedabad–Bhavnagar line is a railway route in the Indian state of Gujarat that connects the major city of Ahmedabad with the coastal city of Bhavnagar, serving as an important regional transport corridor.
  • 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_69d8e51c7c188190b926f3a2a7b5f881 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e654ffb37c8190be540a793befe16c completed April 20, 2026, 4:31 p.m.
Created at: April 10, 2026, 1:50 p.m.