Triple
T6172289
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Molokaʻi Airport |
E137730
|
entity |
| Predicate | hasIATACode |
P2569
|
FINISHED |
| Object | MKK |
E137730
|
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: MKK | Statement: [Molokaʻi Airport, hasIATACode, MKK]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MKK Context triple: [Molokaʻi Airport, hasIATACode, MKK]
-
A.
MKK
chosen
MKK is the IATA airport code for Molokaʻi Airport, the main air gateway to the Hawaiian island of Molokaʻi.
-
B.
MMK
MMK is the three-letter ISO 4217 currency code for the Myanmar kyat, the official currency of Myanmar.
-
C.
KMK
KMK is the central coordinating body of Germany’s state education and cultural ministers, responsible for harmonizing policies across the federal states.
-
D.
MKC
MKC is the IATA airport code for Charles B. Wheeler Downtown Airport, a general aviation and corporate airport serving Kansas City, Missouri.
-
E.
MK
MK is the postal area code designation for Milton Keynes and its surrounding region in the United Kingdom.
- 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_69c008a68c508190a8d78245c865960e |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c05d9319548190980c99f692bd4115 |
completed | March 22, 2026, 9:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c141ad559881909076b6ab34b14f2b |
completed | March 23, 2026, 1:35 p.m. |
Created at: March 22, 2026, 4:18 p.m.