Triple

T22983521
Position Surface form Disambiguated ID Type / Status
Subject JGA E571535 entity
Predicate refersTo P37 FINISHED
Object Jamnagar 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: Jamnagar Airport | Statement: [JGA, refersTo, Jamnagar Airport]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Jamnagar Airport
Context triple: [JGA, refersTo, Jamnagar Airport]
  • A. Jamnagar Airport chosen
    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.
  • B. Jabalpur Airport
    Jabalpur Airport is a domestic airport in Madhya Pradesh, India, serving the city of Jabalpur and its surrounding region.
  • C. Kandla Airport
    Kandla Airport is a domestic airport in Gujarat, India, serving the port city of Kandla and the nearby town of Gandhidham.
  • D. Bareilly Airport
    Bareilly Airport is a domestic airport in Uttar Pradesh, India, serving the city of Bareilly with regional commercial flights and also functioning as an Indian Air Force base.
  • E. 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.
  • 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_69e245b3c50481908bb3741ec9f40862 completed April 17, 2026, 2:37 p.m.
NER Named-entity recognition batch_69f1829775e881909c5d6d35d3fd57f7 completed April 29, 2026, 4:01 a.m.
Created at: April 17, 2026, 3:49 p.m.