Triple
T15658367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kamloops Airport |
E376505
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | YKA |
E376506
|
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: YKA | Statement: [Kamloops Airport, IATAcode, YKA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: YKA Context triple: [Kamloops Airport, IATAcode, YKA]
-
A.
YKA
chosen
YKA is the IATA airport code for Kamloops Airport, a regional airport serving the city of Kamloops in British Columbia, Canada.
-
B.
yka
yka is the ISO 639-3 language code for the Yakan language spoken by the Yakan people of the southern Philippines.
-
C.
KYA
KYA is the IATA airport code for Konya Airport, a public and military airport serving the city of Konya in Turkey.
-
D.
YAK
YAK is the IATA airport code for Yakutat Airport, a public airport serving the community of Yakutat in Alaska, United States.
-
E.
YAKT
YAKT is the time zone abbreviation for Yakutsk Time, used in parts of eastern Russia.
- 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_69d85cd1564c8190991adda63bfab4b0 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04ef3cb8c8190a10815b675b341c1 |
completed | April 16, 2026, 2:52 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ff679bb7f0819092a98c2981bc9267 |
completed | May 9, 2026, 4:58 p.m. |
Created at: April 10, 2026, 4:15 a.m.