Triple
T13045427
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Simferopol International Airport |
E327305
|
entity |
| Predicate | ICAOCode |
P419
|
FINISHED |
| Object | UKFF |
E327305
|
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: UKFF | Statement: [Simferopol International Airport, ICAOCode, UKFF]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: UKFF Context triple: [Simferopol International Airport, ICAOCode, UKFF]
-
A.
UKFF
chosen
UKFF is the ICAO airport code assigned to Simferopol International Airport in Crimea.
-
B.
FKK
FKK is the National Rail station code assigned to Falkirk High railway station in Scotland.
-
C.
UKSF
UKSF is the United Kingdom Special Forces group, an elite military formation that includes units such as the SAS, SBS, and supporting specialist elements.
-
D.
UKK
UKK is the NUTS statistical region code used by the European Union to designate Southwest England for regional analysis and reporting.
-
E.
FKF
FKF is the Football Kenya Federation, the national governing body responsible for organizing and overseeing football activities and competitions in Kenya.
- 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_69d8076e64308190904fb5c93517c901 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d98050157c8190bb8c640b759ac2b7 |
completed | April 10, 2026, 10:57 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6d5fdd04c8190a86dbba1b81c8e6b |
completed | May 3, 2026, 4:58 a.m. |
Created at: April 9, 2026, 8:56 p.m.