Triple
T5257647
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Air Force Thunderbirds |
E118739
|
entity |
| Predicate | tourPattern |
P62556
|
FINISHED |
| Object | annual demonstration season |
—
|
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: annual demonstration season | Statement: [United States Air Force Thunderbirds, tourPattern, annual demonstration season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tourPattern Context triple: [United States Air Force Thunderbirds, tourPattern, annual demonstration season]
-
A.
travelPattern
Indicates the typical routes, frequencies, and behaviors associated with how an entity moves or travels between locations.
-
B.
hasTouristRoute
Indicates that a location or site is connected to or included in a designated tourist route or itinerary.
-
C.
tourDocumented
Indicates that a tour has been recorded or documented, typically capturing its details, events, or progression.
-
D.
tourStopOf
Indicates that one entity is a stop or scheduled visit location within the itinerary or route of another entity’s tour.
-
E.
tourCategory
Indicates the classification or type of a tour (e.g., by theme, style, or purpose) that the tour belongs to.
- F. None of above. chosen
Provenance (4 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. |
| PDg | Predicate description generation | batch_69bd7bcabe58819096255672664513b1 |
completed | March 20, 2026, 4:54 p.m. |
Created at: March 20, 2026, 1:50 p.m.