Triple

T5170672
Position Surface form Disambiguated ID Type / Status
Subject Kansas City International Airport E116668 entity
Predicate icaoCode P419 FINISHED
Object KMCI E116668 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: KMCI | Statement: [Kansas City International Airport, icaoCode, KMCI]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KMCI
Context triple: [Kansas City International Airport, icaoCode, KMCI]
  • A. KMCI chosen
    KMCI is the ICAO code for Kansas City International Airport, a major commercial airport serving the Kansas City metropolitan area in Missouri, USA.
  • B. KCMI
    KCMI is the ICAO airport code for University of Illinois Willard Airport, a public airport serving the Champaign–Urbana area in Illinois, United States.
  • C. KSMF
    KSMF is the ICAO airport code for Sacramento International Airport, a major commercial airport serving California’s capital region.
  • D. KMC
    KMC is the municipal governing body responsible for providing and managing civic services and infrastructure in Karachi, Pakistan.
  • E. KMCO
    KMCO is the ICAO airport code for Orlando International Airport, a major commercial airport serving the Orlando, Florida metropolitan area.
  • 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_69bd445ff97c81909a2615cc56235470 completed March 20, 2026, 12:58 p.m.
NER Named-entity recognition batch_69bd794f44248190a3a90c92208104a7 completed March 20, 2026, 4:43 p.m.
NED1 Entity disambiguation (via context triple) batch_69bee077effc8190bdd5771db64d1578 completed March 21, 2026, 6:16 p.m.
Created at: March 20, 2026, 1:45 p.m.