Triple

T22728641
Position Surface form Disambiguated ID Type / Status
Subject GWL E562065 entity
Predicate represents P129 FINISHED
Object Gwalior 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: Gwalior Airport | Statement: [GWL, represents, Gwalior Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Gwalior Airport
Context triple: [GWL, represents, Gwalior Airport]
  • A. Gwalior Airport chosen
    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.
  • B. Jabalpur Airport
    Jabalpur Airport is a domestic airport in Madhya Pradesh, India, serving the city of Jabalpur and its surrounding region.
  • 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. Vadodara Airport
    Vadodara Airport is a domestic airport in the city of Vadodara, India, serving as one of the key air transport hubs in the state of Gujarat.
  • E. Solapur Airport
    Solapur Airport is a domestic airport in Maharashtra, India, serving the city of Solapur and nearby regions including pilgrimage centers such as Tuljapur.
  • 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_69e24550859c81908727d91efc3a81b4 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1792b22cc819099aa00bb2dbacce3 completed April 29, 2026, 3:21 a.m.
Created at: April 17, 2026, 3:21 p.m.