Triple
T17074592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Enschede Airport Twente |
E414315
|
entity |
| Predicate | militaryUseEnded |
P14594
|
FINISHED |
| Object | 2007 |
—
|
LITERAL 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: 2007 | Statement: [Enschede Airport Twente, militaryUseEnded, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: militaryUseEnded Context triple: [Enschede Airport Twente, militaryUseEnded, 2007]
-
A.
militaryUseEnd
chosen
Indicates the point in time or condition at which the military use of something (such as a facility, resource, or asset) ceases.
-
B.
endOfWeaponsProduction
Indicates that the production or manufacturing of weapons has ceased or been brought to an end.
-
C.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
D.
postMilitaryUse
Indicates that an entity is used or repurposed after its original military function or service has ended.
-
E.
claimedDecommissioningOfWeapons
Indicates that an entity has asserted or reported that certain weapons have been taken out of service or rendered non-operational.
- F. None of above.
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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3dbc3b69c819093b32da3998eed46 |
completed | April 18, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69e35d642f74819098c014135e249b27 |
completed | April 18, 2026, 10:31 a.m. |
Created at: April 10, 2026, 5:34 a.m.