Triple

T23279346
Position Surface form Disambiguated ID Type / Status
Subject KDET E588813 entity
Predicate hasIcaoCode P419 FINISHED
Object KDET 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: KDET | Statement: [KDET, hasIcaoCode, KDET]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: KDET
Context triple: [KDET, hasIcaoCode, KDET]
  • A. KDET chosen
    KDET is the ICAO airport code for Coleman A. Young International Airport, a public airport serving Detroit, Michigan.
  • B. KDEN
    KDEN is the ICAO airport code for Denver International Airport, a major U.S. air hub located in Denver, Colorado.
  • C. KDTW
    KDTW is the ICAO airport code for Detroit Metropolitan Wayne County Airport, a major international air transport hub serving the Detroit, Michigan metropolitan area.
  • D. KDSM
    KDSM is the ICAO airport code for Des Moines International Airport in Des Moines, Iowa, a key commercial aviation hub for the region.
  • E. KRDU
    KRDU is the ICAO airport code for Raleigh–Durham International Airport, a major commercial airport serving North Carolina’s Research Triangle 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_69e25d16e2c08190a291de254703129e completed April 17, 2026, 4:17 p.m.
NER Named-entity recognition batch_69f196419eac819081d0beb5767046dc completed April 29, 2026, 5:25 a.m.
Created at: April 17, 2026, 4:50 p.m.