Triple

T12814150
Position Surface form Disambiguated ID Type / Status
Subject Flagstaff Pulliam Airport E306346 entity
Predicate FAAcode P420 FINISHED
Object FLG E1005606 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: FLG | Statement: [Flagstaff Pulliam Airport, FAAcode, FLG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: FLG
Context triple: [Flagstaff Pulliam Airport, FAAcode, FLG]
  • A. FLG
    FLG is the ICAO airline designator used to identify Endeavor Air in international aviation operations.
  • B. FLG chosen
    FLG is the IATA airport code for Flagstaff Pulliam Airport, a regional airport serving Flagstaff, Arizona, and the surrounding northern Arizona area.
  • C. FLK
    FLK is the ISO 3166-1 alpha-3 country code for the Falkland Islands, a British Overseas Territory in the South Atlantic Ocean.
  • D. FLN
    FLN is an Algerian nationalist political organization and former revolutionary movement that led the struggle for Algeria’s independence from French colonial rule.
  • E. FL-2
    FL-2 is the abbreviation for Florida's 2nd congressional district, a U.S. House of Representatives district covering part of the Florida Panhandle.
  • 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_69d7bdf46c448190b1faa55aaacb6317 completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96e9beb30819097c256a5aab9a4c8 completed April 10, 2026, 9:41 p.m.
NED1 Entity disambiguation (via context triple) batch_69f69b97ffd481909c540f52c781f63f completed May 3, 2026, 12:49 a.m.
Created at: April 9, 2026, 5:31 p.m.