Triple

T20563807
Position Surface form Disambiguated ID Type / Status
Subject Great Falls International Airport E504914 entity
Predicate FAAcode P420 FINISHED
Object GTF E1438703 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: GTF | Statement: [Great Falls International Airport, FAAcode, GTF]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GTF
Context triple: [Great Falls International Airport, FAAcode, GTF]
  • A. GTF chosen
    GTF is the three-letter IATA airport code for Great Falls International Airport in Great Falls, Montana, USA.
  • B. GFF
    GFF is the IATA airport code for Griffith Airport, a regional airport serving Griffith in New South Wales, Australia.
  • C. GFF
    GFF is the commonly used abbreviation for the Georgian Football Federation, the governing body of football in Georgia.
  • D. KGTF
    KGTF is the ICAO airport code for Great Falls International Airport in Great Falls, Montana, United States.
  • E. GDF
    GDF is the Global Drug Facility, an international mechanism that supplies quality-assured medicines and diagnostics to support tuberculosis control and treatment programs worldwide.
  • 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_69e0b4b6587c8190aee63dc7cff244ea completed April 16, 2026, 10:06 a.m.
NER Named-entity recognition batch_69e6a7a0a0488190a534050b40ff47da completed April 20, 2026, 10:24 p.m.
NED1 Entity disambiguation (via context triple) batch_6a08b3ddd76c8190bf8a7ff3b2820188 completed May 16, 2026, 6:13 p.m.
Created at: April 16, 2026, 11:39 a.m.