Triple

T9232685
Position Surface form Disambiguated ID Type / Status
Subject McGhee Tyson Airport E221856 entity
Predicate ICAO code P419 FINISHED
Object KTYS E221857 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: KTYS | Statement: [McGhee Tyson Airport, ICAO code, KTYS]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KTYS
Context triple: [McGhee Tyson Airport, ICAO code, KTYS]
  • A. KTYS chosen
    KTYS is the ICAO airport code for McGhee Tyson Airport, the primary commercial airport serving Knoxville, Tennessee.
  • B. KTW
    KTW is the IATA airport code for Katowice International Airport serving the Silesian region of southern Poland.
  • C. KTTS
    KTTS is the ICAO airport code for the Shuttle Landing Facility at NASA’s Kennedy Space Center in Florida, a specialized runway used primarily for space shuttle and space-related aircraft operations.
  • D. KMSY
    KMSY is the ICAO airport code for Louis Armstrong New Orleans International Airport, the primary commercial airport serving the New Orleans metropolitan area in Louisiana, USA.
  • E. KTUS
    KTUS is the ICAO airport code for Tucson International Airport, a major commercial and military aviation facility serving Tucson, Arizona.
  • 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_69ca83ed628c8190bc02d641e57f097f completed March 30, 2026, 2:08 p.m.
NER Named-entity recognition batch_69ccee1a7e9881908e0c11f242162017 completed April 1, 2026, 10:06 a.m.
NED1 Entity disambiguation (via context triple) batch_69d077bb5b10819083fd2de3ed7d69a4 completed April 4, 2026, 2:30 a.m.
Created at: March 30, 2026, 7:29 p.m.