Triple
T18123343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gary/Chicago International Airport |
E433800
|
entity |
| Predicate | FAA LID |
P420
|
FINISHED |
| Object | GYY |
—
|
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: GYY | Statement: [Gary/Chicago International Airport, FAA LID, GYY]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GYY Context triple: [Gary/Chicago International Airport, FAA LID, GYY]
-
A.
GYY
chosen
GYY is the IATA airport code for Gary/Chicago International Airport, a regional airport serving the Gary, Indiana and greater Chicago metropolitan area.
-
B.
GYI
GYI is the FAA location identifier for North Texas Regional Airport, a public airport serving the Sherman–Denison area in Texas.
-
C.
KGYY
KGYY is the ICAO airport code for Gary/Chicago International Airport, a public airport serving the Gary, Indiana and greater Chicago metropolitan area.
-
D.
YYU
YYU is the IATA airport code for Kapuskasing Airport in Kapuskasing, Ontario, Canada.
-
E.
YZZ
YZZ is the IATA airport code for Trail Regional Airport, a small regional airport serving the Trail area in British Columbia, Canada.
- 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_69d8b909e8cc81908df4cc2b8ea6d11f |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ddebeae88190ae50e9a258b34dbe |
completed | April 19, 2026, 1:51 p.m. |
Created at: April 10, 2026, 10:28 a.m.