Triple
T16835943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mallam Aminu Kano International Airport |
E409277
|
entity |
| Predicate | IATACode |
P418
|
FINISHED |
| Object | KAN |
E409277
|
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: KAN | Statement: [Mallam Aminu Kano International Airport, IATACode, KAN]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KAN Context triple: [Mallam Aminu Kano International Airport, IATACode, KAN]
-
A.
KAN
chosen
KAN is the IATA airport code for Mallam Aminu Kano International Airport, a major airport serving Kano in northern Nigeria.
-
B.
Kan
Kan is a transliteration variant of the title and name "Khan," historically used across Central and South Asia for rulers and nobility.
-
C.
Kan
Kan is the family name of Naoto Kan, a Japanese politician who served as Prime Minister of Japan from 2010 to 2011.
-
D.
KAND
KAND is the ICAO airport code for Anderson Regional Airport in Anderson, South Carolina, United States.
-
E.
Kanai
Kanai was a former municipality in Niigata Prefecture, Japan, that later became part of the city of Sado through a merger.
- 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_69d883952b048190887740a980b712ed |
completed | April 10, 2026, 4:59 a.m. |
| NER | Named-entity recognition | batch_69e3b34d49d08190aa62f05d67244584 |
completed | April 18, 2026, 4:37 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a00bb15c9f48190a4d73bb08a15beb4 |
completed | May 10, 2026, 5:06 p.m. |
Created at: April 10, 2026, 5:23 a.m.