Triple

T13583113
Position Surface form Disambiguated ID Type / Status
Subject Johnson County Executive Airport E324472 entity
Predicate hasICAOIdentifier P36333 FINISHED
Object KOJC E324472 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: KOJC | Statement: [Johnson County Executive Airport, hasICAOIdentifier, KOJC]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KOJC
Context triple: [Johnson County Executive Airport, hasICAOIdentifier, KOJC]
  • A. KOJC chosen
    KOJC is the ICAO airport code for Johnson County Executive Airport, a public general aviation facility serving the Kansas City metropolitan area in Kansas, USA.
  • B. KCJR
    KCJR is the ICAO airport code for Culpeper Regional Airport, a public-use airport serving Culpeper County in Virginia, United States.
  • C. KJYO
    KJYO is the ICAO airport code for Leesburg Executive Airport, a public general aviation airport serving Leesburg, Virginia, in the United States.
  • D. KJKA
    KJKA is the ICAO airport code for Jack Edwards National Airport, a public airport serving Gulf Shores, Alabama.
  • E. KOKC
    KOKC is the ICAO airport code for Will Rogers World Airport, the primary commercial airport serving Oklahoma City, Oklahoma.
  • 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_69d80769100c819099111274614f5ed2 completed April 9, 2026, 8:09 p.m.
NER Named-entity recognition batch_69dbb031e8048190a5f2ea934308036c completed April 12, 2026, 2:46 p.m.
NED1 Entity disambiguation (via context triple) batch_69f77f8deae88190b932a57789c70e77 completed May 3, 2026, 5:02 p.m.
Created at: April 9, 2026, 9:49 p.m.