Triple
T5257638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force Thunderbirds |
E118739
|
entity |
| Predicate | performanceVenues |
P25526
|
FINISHED |
| Object | airshows |
—
|
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: airshows | Statement: [United States Air Force Thunderbirds, performanceVenues, airshows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performanceVenues Context triple: [United States Air Force Thunderbirds, performanceVenues, airshows]
-
A.
originalPerformanceVenue
Indicates the venue where a performance was first originally presented or premiered.
-
B.
legacyVenue
Indicates that a venue has historical or long-standing significance, often preserved or recognized due to its past importance or enduring role.
-
C.
typicalVenues
chosen
Indicates that the specified locations are common or standard places where the associated activity, event, or entity usually occurs or is hosted.
-
D.
performingArtsDomain
Indicates that the subject operates within, is related to, or is characterized by the field of performing arts.
-
E.
primaryVenues
Indicates the main or most important venues associated with or used by a given entity.
- 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_69bd446978108190bb5f9c5c23d93f88 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7bcced6881909bdb7ac5471a37fe |
completed | March 20, 2026, 4:54 p.m. |
| PD | Predicate disambiguation | batch_69bd77c55224819096c0bcfcfae79bd3 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:50 p.m.