Triple

T6504020
Position Surface form Disambiguated ID Type / Status
Subject Piedmont Triad International Airport E148960 entity
Predicate ICAOcode P419 FINISHED
Object KGSO E552980 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: KGSO | Statement: [Piedmont Triad International Airport, ICAOcode, KGSO]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KGSO
Context triple: [Piedmont Triad International Airport, ICAOcode, KGSO]
  • A. KGSO chosen
    KGSO is the ICAO airport code for Piedmont Triad International Airport in Greensboro, North Carolina.
  • B. KGX
    KGX is the National Rail station code for London King's Cross, a major central London railway terminus and transport hub.
  • C. KSGH
    KSGH is the ICAO airport code for Springfield–Beckley Municipal Airport in Springfield, Ohio, United States.
  • D. KIAH
    KIAH is the ICAO airport code for George Bush Intercontinental Airport, a major international airport serving the Houston, Texas metropolitan area.
  • E. KGSP
    KGSP is the ICAO airport code for Greenville–Spartanburg International Airport, a major commercial airport serving the Upstate region of South Carolina, USA.
  • 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_69c687e9ad288190bae5bcac9c8ac855 completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c69965c8448190b9eb0c50711dd44f completed March 27, 2026, 2:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69c6cb3c524481909d9c822e928dc821 completed March 27, 2026, 6:23 p.m.
Created at: March 27, 2026, 1:42 p.m.