Triple
T16363112
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kigali International Airport |
E397365
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | KGL |
E397366
|
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: KGL | Statement: [Kigali International Airport, IATAcode, KGL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KGL Context triple: [Kigali International Airport, IATAcode, KGL]
-
A.
KGL
chosen
KGL is the IATA airport code for Kigali International Airport, the main air gateway to Rwanda’s capital city.
-
B.
KLGC
KLGC is the ICAO airport code for LaGrange–Callaway Airport, a public-use airport serving LaGrange, Georgia, in the United States.
-
C.
KGN
KGN is the standard three-letter abbreviation used for the Kingston Frontenacs, a major junior ice hockey team in the Ontario Hockey League.
-
D.
KGG
KGG is the abbreviated name of Kings Guard Gaming, an NBA 2K League esports team affiliated with the Sacramento Kings.
-
E.
KGV
KGV is the station code for Kingsgrove railway station on Sydney’s suburban rail network in New South Wales, Australia.
- 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_69d87f2778dc8190aa95c7572db127e6 |
completed | April 10, 2026, 4:40 a.m. |
| NER | Named-entity recognition | batch_69e2ff3aada88190a6e01f04c494a6ac |
completed | April 18, 2026, 3:49 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a002dbeabe081909e3d02676293e8b2 |
completed | May 10, 2026, 7:03 a.m. |
Created at: April 10, 2026, 5:08 a.m.