Triple

T20569130
Position Surface form Disambiguated ID Type / Status
Subject Topeka Regional Airport E505043 entity
Predicate hasICAOCode P419 FINISHED
Object KFOE 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: KFOE | Statement: [Topeka Regional Airport, hasICAOCode, KFOE]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KFOE
Context triple: [Topeka Regional Airport, hasICAOCode, KFOE]
  • A. KFOE chosen
    KFOE is the ICAO airport code for Topeka Regional Airport, a public/military airfield serving Topeka, Kansas.
  • B. KFOK
    KFOK is the ICAO airport code for Francis S. Gabreski Airport, a public and military airfield in Westhampton Beach, New York.
  • C. KFFO
    KFFO is the ICAO airport code for Wright-Patterson Air Force Base, a major U.S. Air Force installation near Dayton, Ohio.
  • D. KFXE
    KFXE is the ICAO airport code for Fort Lauderdale Executive Airport, a busy general aviation and corporate aviation facility in Fort Lauderdale, Florida.
  • E. KBFR
    KBFR is the ICAO airport code for Virgil I. Grissom Municipal Airport in Bedford, Indiana, United States.
  • 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_69e0b4b721588190993ac7b0a9be2736 completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a7a4b90c81909854dac72f671eec completed April 20, 2026, 10:24 p.m.
Created at: April 16, 2026, 11:39 a.m.