Triple
T8799165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inyokern Airport |
E209357
|
entity |
| Predicate | FAAcode |
P420
|
FINISHED |
| Object | IYK |
E759831
|
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: IYK | Statement: [Inyokern Airport, FAAcode, IYK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IYK Context triple: [Inyokern Airport, FAAcode, IYK]
-
A.
IYK
chosen
IYK is the IATA airport code for Inyokern Airport, a public airport serving the Inyokern area in California, United States.
-
B.
IY
IY is one of the Zilog Z80 CPU’s 16-bit index registers, primarily used for indexed addressing operations.
-
C.
YKA
YKA is the IATA airport code for Kamloops Airport, a regional airport serving the city of Kamloops in British Columbia, Canada.
-
D.
YIA
YIA is the IATA airport code for Yogyakarta International Airport, the main commercial air gateway serving the Yogyakarta region in Indonesia.
-
E.
YKF
YKF is the IATA airport code for Region of Waterloo International Airport serving the Kitchener–Waterloo area in Ontario, Canada.
- 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_69ca836240888190a62b262e56a69d2f |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5fb7491c8190bcdb98d6cc003d9e |
completed | March 31, 2026, 11:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cf891583d48190ba276b5a1f7d6f7a |
completed | April 3, 2026, 9:32 a.m. |
Created at: March 30, 2026, 6:44 p.m.