Triple
T2212178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kona International Airport |
E50941
|
entity |
| Predicate | hasCode |
P9567
|
FINISHED |
| Object | KOA |
E245721
|
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: KOA | Statement: [Kona International Airport, hasCode, KOA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KOA Context triple: [Kona International Airport, hasCode, KOA]
-
A.
KOA
chosen
KOA is the three-letter IATA airport code for Kona International Airport on the island of Hawaiʻi.
-
B.
Koop
Koop is a surname most prominently associated with C. Everett Koop, the influential former Surgeon General of the United States.
-
C.
Kohat
Kohat is a historic city in northwestern Pakistan known for its strategic location, military cantonment, and role as a regional administrative and commercial center.
-
D.
KIX
KIX is the three-letter IATA airport code for Kansai International Airport serving the Osaka region of Japan.
-
E.
Koht
Koht is a Norwegian surname most notably associated with historian and politician Halvdan Koht.
- 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_69a88b06709c8190978fb2418470d1b6 |
completed | March 4, 2026, 7:41 p.m. |
| NER | Named-entity recognition | batch_69abbfecea6c8190b762bbfda8490e31 |
completed | March 7, 2026, 6:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae71b629088190a5228a2f68500bd5 |
completed | March 9, 2026, 7:07 a.m. |
Created at: March 4, 2026, 7:46 p.m.