Triple
T8269168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lutsk Airport |
E193377
|
entity |
| Predicate | locatedOn |
P40
|
FINISHED |
| Object | Lutsk airfield |
E193377
|
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: Lutsk airfield | Statement: [Lutsk Airport, locatedOn, Lutsk airfield]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lutsk airfield Context triple: [Lutsk Airport, locatedOn, Lutsk airfield]
-
A.
Lutsk Airport
chosen
Lutsk Airport is a regional civil and military airfield serving the city of Lutsk and the surrounding area in western Ukraine.
-
B.
Zhytomyr Airport
Zhytomyr Airport is a regional civil airport serving the city of Zhytomyr in northwestern Ukraine.
-
C.
Leszno-Strzyżewice airfield
Leszno-Strzyżewice airfield is a regional aviation facility in Leszno, Poland, known especially for sport and glider flying activities.
-
D.
Kbely Air Base
Kbely Air Base is a major military airfield near Prague that serves as one of the principal operational and logistical hubs of the Czech Air Force.
-
E.
Malbork Air Base
Malbork Air Base is a Polish military airfield that serves as a key NATO outpost for air defense missions over the Baltic region.
- 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_69ca82e14ae481908ffdb822cd2192bc |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb795127ac81908196008f5579f83f |
completed | March 31, 2026, 7:35 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd683d04e081908b0ce81e866f0311 |
completed | April 1, 2026, 6:47 p.m. |
Created at: March 30, 2026, 5:50 p.m.