Triple
T22723169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GEG |
E561918
|
entity |
| Predicate | hasFAAIdentifier |
P420
|
FINISHED |
| Object | GEG |
—
|
NE NERFINISHED |
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: [GEG, hasFAAIdentifier, GEG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GEG Context triple: [GEG, hasFAAIdentifier, GEG]
-
A.
GEG
chosen
GEG is the three-letter IATA airport code for Spokane International Airport in Spokane, Washington.
-
B.
GEZ
GEZ (Gebühreneinzugszentrale) was the former German public broadcasting fee collection agency responsible for administering and collecting mandatory license fees for public radio and television.
-
C.
Geg
Geg is an alternative name for Gheg, the northern dialect group of the Albanian language spoken primarily in northern Albania and surrounding regions.
-
D.
GEC
GEC is the ICAO airline designator used by Lufthansa Cargo, the air freight division of Lufthansa.
-
E.
GEC
GEC (General Electric Company) was a major British industrial conglomerate known for its extensive activities in electronics, electrical engineering, and defense.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f17927e0348190a4dba430563ef155 |
completed | April 29, 2026, 3:21 a.m. |
Created at: April 17, 2026, 3:20 p.m.