Triple
T23282879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Royal International Air Tattoo |
E588913
|
entity |
| Predicate | primaryVenueSince |
P17127
|
FINISHED |
| Object | RAF Fairford |
—
|
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: RAF Fairford | Statement: [Royal International Air Tattoo, primaryVenueSince, RAF Fairford]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryVenueSince Context triple: [Royal International Air Tattoo, primaryVenueSince, RAF Fairford]
-
A.
primaryVenueFor
Indicates that one entity serves as the main or principal venue or location for events, activities, or operations associated with another entity.
-
B.
usualVenueSince
chosen
Indicates that a particular venue has been the regular or customary location for something (e.g., an event or activity) starting from a specified point in time.
-
C.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
-
D.
earlyVenue
Indicates that an event or activity takes place at a venue earlier than a standard, expected, or comparative time.
-
E.
previousVenue
Indicates that one venue was used or occupied before another in a sequence of venues.
- 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_69e25d16e2c08190a291de254703129e |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f196447a748190bd797ec9baa63fc3 |
completed | April 29, 2026, 5:25 a.m. |
| PD | Predicate disambiguation | batch_69effcecabd88190856fb6e1d993e4dd |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:58 p.m.