Triple

T18096357
Position Surface form Disambiguated ID Type / Status
Subject Mobile Downtown Airport E433097 entity
Predicate ICAO code P419 FINISHED
Object KBFM 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: KBFM | Statement: [Mobile Downtown Airport, ICAO code, KBFM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KBFM
Context triple: [Mobile Downtown Airport, ICAO code, KBFM]
  • A. KBFM chosen
    KBFM is the ICAO airport code for Mobile Downtown Airport, a public airport serving the city of Mobile, Alabama, in the United States.
  • B. KCBM
    KCBM is the ICAO airport code for Columbus Air Force Base, a United States Air Force installation in Mississippi used primarily for pilot training operations.
  • C. KBIF
    KBIF is the ICAO airport code for Biggs Army Airfield, a U.S. military airfield located at Fort Bliss in El Paso, Texas.
  • D. KBFR
    KBFR is the ICAO airport code for Virgil I. Grissom Municipal Airport in Bedford, Indiana, United States.
  • E. KBFI
    KBFI is the ICAO airport code for King County International Airport (Boeing Field), a major general aviation and aerospace testing airport located in Seattle, Washington.
  • 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_69d8b907d05c819083cc3bd6021089e6 completed April 10, 2026, 8:47 a.m.
NER Named-entity recognition batch_69e4dd1c56848190be0b8c80b30dba6c completed April 19, 2026, 1:48 p.m.
Created at: April 10, 2026, 10:27 a.m.