Triple
T18269934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tiksi Airport |
E437579
|
entity |
| Predicate | IATA code |
P2569
|
FINISHED |
| Object | IKS |
—
|
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: IKS | Statement: [Tiksi Airport, IATA code, IKS]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IKS Context triple: [Tiksi Airport, IATA code, IKS]
-
A.
IKS
chosen
IKS is the IATA airport code for Tiksi Airport, which serves the settlement of Tiksi in the Sakha Republic of Russia.
-
B.
IKS
IKS is a Fraunhofer research institute focused on developing safe, reliable, and intelligent cognitive systems and AI technologies for industry and society.
-
C.
IXS
IXS is the three-letter IATA airport code assigned to Silchar Airport in Assam, India.
-
D.
IK
IK is the IATA airport code for IKAR, identifying it within the international air transport system.
-
E.
KIX
KIX is the three-letter IATA airport code for Kansai International Airport serving the Osaka region of Japan.
- 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_69d8b913351c8190932b6a426de04b41 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4ff7d4f88819084123ed6c9e7e5b8 |
completed | April 19, 2026, 4:14 p.m. |
Created at: April 10, 2026, 10:34 a.m.