Triple
T17825970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince George Airport |
E445118
|
entity |
| Predicate | ICAOcode |
P419
|
FINISHED |
| Object | CYXS |
—
|
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: CYXS | Statement: [Prince George Airport, ICAOcode, CYXS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: CYXS Context triple: [Prince George Airport, ICAOcode, CYXS]
-
A.
CYXD
CYXD is the former ICAO airport code for Edmonton City Centre Airport, a now-closed airport that once served downtown Edmonton, Alberta, Canada.
-
B.
YXS
chosen
YXS is the IATA airport code for Prince George Airport, a regional air transport hub serving Prince George in central British Columbia, Canada.
-
C.
CYXE
CYXE is the ICAO airport code for Saskatoon John G. Diefenbaker International Airport in Saskatoon, Saskatchewan, Canada.
-
D.
YXU
YXU is the IATA airport code for London International Airport serving London, Ontario, Canada.
-
E.
YX
YX is the IATA airline designator used by Republic Airways, a major U.S. regional airline operating flights on behalf of larger carriers.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e48914226c819083edcc78e00b2d42 |
completed | April 19, 2026, 7:49 a.m. |
Created at: April 10, 2026, 10:15 a.m.