Triple

T13053754
Position Surface form Disambiguated ID Type / Status
Subject Lal Bahadur Shastri International Airport E327512 entity
Predicate locatedIn P40 FINISHED
Object Babathpur E328805 NE FINISHED

How this triple was built (2 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: Babathpur | Statement: [Lal Bahadur Shastri International Airport, locatedIn, Babathpur]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Babathpur
Context triple: [Lal Bahadur Shastri International Airport, locatedIn, Babathpur]
  • A. Babatpur chosen
    Babatpur is a locality near Varanasi in the Indian state of Uttar Pradesh, known primarily for hosting the city’s main airport.
  • B. Brahmapuri
    Brahmapuri is a town in Maharashtra, India, known as one of the important urban centers within Chandrapur district.
  • C. Bhagwanpura
    Bhagwanpura is a town in the Khargone district of Madhya Pradesh, India, known primarily as a local administrative and market center for surrounding rural areas.
  • D. Mominpura
    Mominpura is a locality in Nagpur, Maharashtra, India, known as a densely populated residential and commercial area with a significant Muslim community.
  • E. Ghoghardiha
    Ghoghardiha is a town located in the Madhubani district of the Indian state of Bihar.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69d8076e64308190904fb5c93517c901 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69d980bb52d88190b5be12000e27a2c9 completed April 10, 2026, 10:59 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6cbdcc3e881908d9a246558b1c20e completed May 3, 2026, 4:15 a.m.
Created at: April 9, 2026, 8:58 p.m.