Triple
T15277142
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kurumoch International Airport |
E365170
|
entity |
| Predicate | IATAcode |
P418
|
FINISHED |
| Object | KUF |
E256959
|
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: KUF | Statement: [Kurumoch International Airport, IATAcode, KUF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: KUF Context triple: [Kurumoch International Airport, IATAcode, KUF]
-
A.
KUF
chosen
KUF is the IATA airport code for Kurumoch International Airport serving the Samara region in Russia.
-
B.
KFU
KFU is a major Russian research and educational institution officially known as Kazan (Volga Region) Federal University.
-
C.
KAF
KAF is the Kenya Air Force, the aerial warfare branch of the Kenya Defence Forces responsible for defending Kenyan airspace and providing air support to military operations.
-
D.
KHUF
KHUF is the ICAO airport code for Terre Haute Regional Airport, a public airport serving Terre Haute, Indiana, in the United States.
-
E.
KUV
KUV is the IATA airport code for Kunsan Air Base, a United States Air Force installation located in South Korea.
- 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_69d85a103d9081908c1ea6c4c73ac8e3 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00953bc848190b83919f39d5ee37b |
completed | April 15, 2026, 9:55 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69feef734f488190951d029183d456f5 |
completed | May 9, 2026, 8:25 a.m. |
Created at: April 10, 2026, 3:14 a.m.