Triple
T18335318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Olympia Fitness & Performance Weekend |
E439256
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | multi-sport festival |
C735
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: multi-sport festival Context triple: [Olympia Fitness & Performance Weekend, instanceOf, multi-sport festival]
-
A.
multi-sport event
chosen
A multi-sport event is a large-scale organized competition in which athletes from various regions or groups compete across multiple different sports within a unified program and schedule.
-
B.
athletic festival
An athletic festival is a planned event featuring a variety of sports competitions, physical activities, and related celebrations that bring participants and spectators together in a communal setting.
-
C.
biennial sporting event
A biennial sporting event is an organized athletic competition or series of competitions that takes place once every two years, often featuring recurring participants, standardized rules, and a consistent thematic or regional focus.
-
D.
participation in multi-sport event
Participation in multi-sport event represents an individual's or team's involvement in a competitive gathering that features multiple different sports or disciplines under a unified organizational framework.
-
E.
international sporting event series
An international sporting event series is a recurring sequence of organized sports competitions held across multiple countries, featuring athletes or teams from different nations competing under a unified structure or brand.
- F. None of above.
Provenance (1 batch)
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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:36 a.m.