Triple

T22812765
Position Surface form Disambiguated ID Type / Status
Subject Des Moines International Airport E565024 entity
Predicate hasCode P9567 FINISHED
Object KDSM NE NERFINISHED

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: KDSM | Statement: [Des Moines International Airport, hasCode, KDSM]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KDSM
Context triple: [Des Moines International Airport, hasCode, KDSM]
  • A. KDSM chosen
    KDSM is the ICAO airport code for Des Moines International Airport in Des Moines, Iowa, a key commercial aviation hub for the region.
  • B. KCSM
    KCSM is the Mexican subsidiary of the Kansas City Southern railway company, operating freight rail services across key industrial and cross-border corridors in Mexico.
  • C. KRDM
    KRDM is the ICAO airport code for Redmond Municipal Airport, a public airport serving the city of Redmond in central Oregon, United States.
  • D. KRDG
    KRDG is the ICAO airport code for Reading Regional Airport, a public airport serving Reading, Pennsylvania, in the United States.
  • E. KALB
    KALB is the ICAO airport code for Albany International Airport, a major commercial airport serving New York’s Capital Region.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17d61c6f081908d3911710b3aff51 completed April 29, 2026, 3:39 a.m.
Created at: April 17, 2026, 3:32 p.m.