Triple

T12431697
Position Surface form Disambiguated ID Type / Status
Subject Katihar E297044 entity
Predicate hasAirportNearby P4363 FINISHED
Object Bagdogra Airport E163226 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: Bagdogra Airport | Statement: [Katihar, hasAirportNearby, Bagdogra Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Bagdogra Airport
Context triple: [Katihar, hasAirportNearby, Bagdogra Airport]
  • A. Bagdogra Airport chosen
    Bagdogra Airport is a major international airport in northern West Bengal, India, serving as a key gateway to the Darjeeling, Sikkim, and eastern Himalayan regions.
  • B. Darbhanga Airport
    Darbhanga Airport is a domestic airport in Bihar, India, serving the city of Darbhanga and surrounding regions with commercial flight connectivity.
  • C. Dibrugarh Airport
    Dibrugarh Airport is a domestic airport in the Indian state of Assam that serves the city of Dibrugarh and the surrounding Upper Assam region.
  • D. Tezpur Airport
    Tezpur Airport is a domestic airport in Tezpur, Assam, India, serving as a regional air transport hub for the surrounding area.
  • E. Dimapur Airport
    Dimapur Airport is a domestic airport in Nagaland, India, serving as the primary air gateway to the state capital, Kohima, and surrounding regions.
  • 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_69d6ada0640c81908c061d7fb3d47786 completed April 8, 2026, 7:33 p.m.
NER Named-entity recognition batch_69d94d7f2fd08190ab959742dbd8f9c0 completed April 10, 2026, 7:20 p.m.
NED1 Entity disambiguation (via context triple) batch_69f6349d29c481909a37fd386cc06575 completed May 2, 2026, 5:30 p.m.
Created at: April 8, 2026, 9:55 p.m.