Triple

T8011924
Position Surface form Disambiguated ID Type / Status
Subject Bermuda International Airport E186513 entity
Predicate hasICAOcode P419 FINISHED
Object TXKF E171513 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: TXKF | Statement: [Bermuda International Airport, hasICAOcode, TXKF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TXKF
Context triple: [Bermuda International Airport, hasICAOcode, TXKF]
  • A. TXKF chosen
    TXKF is the ICAO airport code for L.F. Wade International Airport, the primary international gateway to Bermuda.
  • B. TXK
    TXK is the IATA airport code for Texarkana Regional Airport, which serves the Texarkana area in Texas and Arkansas.
  • 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. KJAX
    KJAX is the ICAO airport code for Jacksonville International Airport, a major commercial airport serving Jacksonville, Florida.
  • E. KTIW
    KTIW is the ICAO airport code for Tacoma Narrows Airport, a public general aviation airport serving the Tacoma, Washington 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_69ca82abaffc8190ab8af79cdbc31ab3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3d722fbc8190b22745b581421f16 completed March 31, 2026, 3:20 a.m.
NED1 Entity disambiguation (via context triple) batch_69cc56acfcf88190a0e694f60f2907d2 completed March 31, 2026, 11:20 p.m.
Created at: March 30, 2026, 5:19 p.m.