Triple

T19262613
Position Surface form Disambiguated ID Type / Status
Subject JLR E481685 entity
Predicate airportName P4100 FINISHED
Object Jabalpur Airport NE NERFINISHED

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: Jabalpur Airport | Statement: [JLR, airportName, Jabalpur Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jabalpur Airport
Context triple: [JLR, airportName, Jabalpur Airport]
  • A. Jabalpur Airport chosen
    Jabalpur Airport is a domestic airport in Madhya Pradesh, India, serving the city of Jabalpur and its surrounding region.
  • B. Gwalior Airport
    Gwalior Airport is a domestic airport in Gwalior, Madhya Pradesh, India, serving as a regional hub for passenger flights connecting the city to major Indian destinations.
  • C. Jamnagar Airport
    Jamnagar Airport is a domestic airport in Jamnagar, Gujarat, India, serving as a key regional hub for civilian flights and nearby industrial and defense facilities.
  • D. Khajuraho Airport
    Khajuraho Airport is a domestic airport in Madhya Pradesh, India, serving the town of Khajuraho and its famous UNESCO-listed temple complex.
  • E. Jagdalpur Airport
    Jagdalpur Airport is a regional domestic airport serving the city of Jagdalpur in the Bastar district of Chhattisgarh, India.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d8e8ce54cc8190998418ff1f66ef28 completed April 10, 2026, 12:10 p.m.
NER Named-entity recognition batch_69e5fb8ac1a8819094309db4a2e6b163 completed April 20, 2026, 10:10 a.m.
Created at: April 10, 2026, 1:28 p.m.