Triple
T1221199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RAF Waddington |
E26224
|
entity |
| Predicate | airShowStatus |
P16353
|
FINISHED |
| Object | air show discontinued after 2014 |
—
|
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: air show discontinued after 2014 | Statement: [RAF Waddington, airShowStatus, air show discontinued after 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airShowStatus Context triple: [RAF Waddington, airShowStatus, air show discontinued after 2014]
-
A.
hasAirshows
chosen
Indicates that an entity regularly hosts or features airshows as events.
-
B.
hasAircraftOnDisplay
Indicates that an entity exhibits or presents an aircraft as part of a display or collection.
-
C.
exhibitStatus
Indicates the current state or condition of an exhibit within a display, collection, or presentation context.
-
D.
airTraffic
Indicates the movement and flow of aircraft through airspace, including their routes, density, and interactions while in flight.
-
E.
hasAerobaticDisplayTeam
Indicates that an entity maintains or is associated with a team that performs aerobatic flying displays.
- 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_69a49484688c8190a1bf285eb396a8b6 |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be206c108190bb8a5d44fc516c98 |
completed | March 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69a4bb644af08190ba25905f20adb01a |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.