Triple

T22327277
Position Surface form Disambiguated ID Type / Status
Subject Belize City Municipal Airport E551931 entity
Predicate hasIATACode P2569 FINISHED
Object TZA E551931 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: TZA | Statement: [Belize City Municipal Airport, hasIATACode, TZA]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: TZA
Context triple: [Belize City Municipal Airport, hasIATACode, TZA]
  • A. TZA chosen
    TZA is the IATA airport code for Belize City Municipal Airport, a domestic airport serving Belize City in Belize.
  • B. Tiszanána
    Tiszanána is a village in northern Hungary known for its proximity to the Tisza River and recreational areas around Lake Tisza.
  • C. Tansaniaweg
    Tansaniaweg is a street in Berlin’s Afrikanisches Viertel, named in reference to the East African country Tanzania and its historical connections to Germany.
  • D. Zimba
    Zimba is a prominent and jagged limestone mountain peak in the Rätikon range of the Alps, popular with climbers for its striking horn-like shape.
  • E. Wedza
    Wedza is a rural district and township in northeastern Zimbabwe known for its agriculture and gold deposits.
  • 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_69e11e482f788190b78d1588fc26d606 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f157693460819087c165481eb9e128 completed April 29, 2026, 12:57 a.m.
NED1 Entity disambiguation (via context triple) batch_6a0ad520b1c081908fd6de0de24e2d87 completed May 18, 2026, 9 a.m.
Created at: April 16, 2026, 8:42 p.m.