Triple

T14992709
Position Surface form Disambiguated ID Type / Status
Subject Burke Lakefront Airport E373876 entity
Predicate hasICAOCode P419 FINISHED
Object KBKL E373876 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: KBKL | Statement: [Burke Lakefront Airport, hasICAOCode, KBKL]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KBKL
Context triple: [Burke Lakefront Airport, hasICAOCode, KBKL]
  • A. KBKL chosen
    KBKL is the ICAO airport code for Burke Lakefront Airport, a public airport located on the shore of Lake Erie in Cleveland, Ohio.
  • B. KLBF
    KLBF is the ICAO airport code for North Platte Regional Airport in North Platte, Nebraska, United States.
  • C. KBKF
    KBKF is the ICAO airport code for Buckley Space Force Base, a U.S. military installation and airfield located in Aurora, Colorado.
  • D. KLBE
    KLBE is the ICAO airport code for Arnold Palmer Regional Airport in Latrobe, Pennsylvania, United States.
  • E. KBAB
    KBAB is the ICAO airport code for Beale Air Force Base, a major United States Air Force installation in California known for hosting high-altitude reconnaissance aircraft.
  • 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_69d85ccc84388190aa151e5173370c8d completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded715db408190b44e8a8452c79764 completed April 15, 2026, 12:08 a.m.
NED1 Entity disambiguation (via context triple) batch_69fe969842848190a030db797c851fed completed May 9, 2026, 2:06 a.m.
Created at: April 10, 2026, 2:53 a.m.