Triple

T6018612
Position Surface form Disambiguated ID Type / Status
Subject Spokane International Airport E134008 entity
Predicate FAA LID P420 FINISHED
Object GEG E561918 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: GEG | Statement: [Spokane International Airport, FAA LID, GEG]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: GEG
Context triple: [Spokane International Airport, FAA LID, GEG]
  • A. GEG chosen
    GEG is the three-letter IATA airport code for Spokane International Airport in Spokane, Washington.
  • B. Geg
    Geg is an alternative name for Gheg, the northern dialect group of the Albanian language spoken primarily in northern Albania and surrounding regions.
  • C. .ge
    .ge is the country code top-level domain (ccTLD) assigned to websites associated with Georgia.
  • D. CGE
    CGE is a French association that brings together the country’s leading grandes écoles, representing elite higher education and research institutions.
  • E. CGE
    CGE is the abbreviation for Compagnie Générale d’Electricité, a former major French industrial and telecommunications conglomerate.
  • 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_69c008742a5c8190b9cb9c2787a3d8b3 completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c04f8589d0819089ae7840461640f6 completed March 22, 2026, 8:22 p.m.
NED1 Entity disambiguation (via context triple) batch_69c1136a4720819092bf2c6a9101c71b completed March 23, 2026, 10:18 a.m.
Created at: March 22, 2026, 4:07 p.m.