Triple
T19172450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moi Air Base, Nairobi |
E469356
|
entity |
| Predicate | hasIcaoCode |
P419
|
FINISHED |
| Object | HKMO |
—
|
NE NERFINISHED |
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: HKMO | Statement: [Moi Air Base, Nairobi, hasIcaoCode, HKMO]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HKMO Context triple: [Moi Air Base, Nairobi, hasIcaoCode, HKMO]
-
A.
HKMO
chosen
HKMO is the ICAO airport code for Moi International Airport, a major international airport serving Mombasa, Kenya.
-
B.
HKJK
HKJK is the ICAO airport code for Jomo Kenyatta International Airport, the main international gateway serving Nairobi, Kenya.
-
C.
KMHK
KMHK is the ICAO airport code for Manhattan Regional Airport, a public airport serving Manhattan, Kansas, in the United States.
-
D.
MHK
MHK is the FAA airport code for Manhattan Regional Airport, a commercial airport serving Manhattan, Kansas, and the surrounding region.
-
E.
MHK
MHK is the post-nominal abbreviation used by elected members of the House of Keys, the lower branch of the Isle of Man's parliament.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16544948190bd10ca7804dd27a5 |
completed | April 20, 2026, 9:27 a.m. |
Created at: April 10, 2026, 12:06 p.m.