Triple
T5853487
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phoenix Goodyear Airport |
E130093
|
entity |
| Predicate | FAAIdentifier |
P420
|
FINISHED |
| Object | GYR |
E550237
|
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: GYR | Statement: [Phoenix Goodyear Airport, FAAIdentifier, GYR]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GYR Context triple: [Phoenix Goodyear Airport, FAAIdentifier, GYR]
-
A.
GYR
chosen
GYR is the IATA airport code for Phoenix Goodyear Airport, a general aviation and aircraft maintenance facility serving the Phoenix, Arizona area.
-
B.
GYD
GYD is the official currency code for the Guyanese dollar, the national currency of Guyana.
-
C.
YG
YG is an American rapper and songwriter known for his West Coast gangsta rap style and hits like "My Nigga" and "Big Bank."
-
D.
GYI
GYI is the FAA location identifier for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas.
-
E.
KGYR
KGYR is the ICAO airport code for Phoenix Goodyear Airport, a public airport serving the Goodyear area near Phoenix, Arizona.
- 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_69c0084de39081909eb34e6bed74215a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c035529cf88190acc547ae839950e7 |
completed | March 22, 2026, 6:30 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c0b105fb588190ac58a94513df6682 |
completed | March 23, 2026, 3:18 a.m. |
Created at: March 22, 2026, 3:55 p.m.