Triple
T2177781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Key West International Airport |
E48570
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | EYW |
E242997
|
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: EYW | Statement: [Key West International Airport, FAAcode, EYW]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: EYW Context triple: [Key West International Airport, FAAcode, EYW]
-
A.
EYW
chosen
EYW is the IATA airport code for Key West International Airport, a small commercial airport serving Key West in the Florida Keys, USA.
-
B.
YEO
YEO is the IATA airport code for RNAS Yeovilton, a major Royal Navy air station in Somerset, England.
-
C.
YOW
YOW is the three-letter IATA airport code for Ottawa Macdonald–Cartier International Airport, the primary airport serving Canada’s capital city, Ottawa.
-
D.
YV
YV is the IATA airline designator used to identify Mesa Airlines in flight schedules and ticketing systems.
-
E.
ELY
ELY is a historic cathedral city in Cambridgeshire, England, known for its prominent Ely Cathedral and picturesque setting in the Fens.
- 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_69a88aa3faa48190995b233af6525815 |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abbeee0a988190b0729f9070aa4503 |
completed | March 7, 2026, 6 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae653de18481909c3521e060540a38 |
completed | March 9, 2026, 6:14 a.m. |
Created at: March 4, 2026, 7:45 p.m.