Triple
T10423406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kona International Airport |
E245722
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | PHKO |
E245722
|
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: PHKO | Statement: [Kona International Airport, hasICAOCode, PHKO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: PHKO Context triple: [Kona International Airport, hasICAOCode, PHKO]
-
A.
PHKO
chosen
PHKO is the ICAO airport code for Kona International Airport serving the Kona district on Hawaii’s Big Island.
-
B.
KHOP
KHOP is the ICAO airport code for Campbell Army Airfield, a U.S. military airfield located at Fort Campbell on the Kentucky–Tennessee border.
-
C.
POK
POK is the National Rail station code for Pokesdown railway station in Bournemouth, England.
-
D.
KPAH
KPAH is the ICAO airport code for Barkley Regional Airport, a public airport serving the Paducah, Kentucky area in the United States.
-
E.
KPAO
KPAO is the ICAO airport code for Palo Alto Airport, a busy general aviation facility serving the Palo Alto and greater Silicon Valley area in California.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2de4d48190aee65b3f6ec3cc48 |
completed | April 7, 2026, 11:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d7fc2160208190b6384190d9537df4 |
completed | April 9, 2026, 7:21 p.m. |
Created at: April 6, 2026, 12:12 p.m.