Triple
T9844786
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMKG |
E239312
|
entity |
| Predicate | hasICAOCode |
P419
|
FINISHED |
| Object | KMKG |
E239312
|
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: KMKG | Statement: [KMKG, hasICAOCode, KMKG]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KMKG Context triple: [KMKG, hasICAOCode, KMKG]
-
A.
KMKG
chosen
KMKG is the ICAO airport code for Muskegon County Airport in Muskegon, Michigan, United States.
-
B.
KMG
KMG is the IATA airport code for Kunming Changshui International Airport, a major air transport hub serving Kunming in Yunnan Province, China.
-
C.
KGM
KGM is the Turkish General Directorate of Highways, the national authority responsible for planning, constructing, and maintaining Turkey’s road network.
-
D.
KMGM
KMGM is the ICAO airport code for Montgomery Regional Airport, a public airport serving Montgomery, Alabama.
-
E.
KMKE
KMKE is the ICAO airport code for Milwaukee Mitchell International Airport, a major commercial airport serving the Milwaukee, Wisconsin area.
- 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb35dc29c819080203be5b904dc9d |
completed | April 2, 2026, 12:07 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1e42edd98819092d07139890d83e4 |
completed | April 5, 2026, 4:25 a.m. |
Created at: March 30, 2026, 8:33 p.m.