Triple
T30663079
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vans Triple Crown of Skateboarding |
E780584
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | skateboarding competition series |
C57342
|
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: skateboarding competition series Context triple: [Vans Triple Crown of Skateboarding, instanceOf, skateboarding competition series]
-
A.
snowboarding competition series
A snowboarding competition series is a structured sequence of snowboard events held over a season or defined period, where riders accumulate results or points across multiple contests to determine overall rankings or champions.
-
B.
BMX racing series
A BMX racing series is a structured sequence of competitive bicycle motocross events where riders accumulate points across multiple races to determine overall rankings and champions.
-
C.
skeleton competition series
A skeleton competition series is a structured sequence of skeleton races in which athletes compete individually over multiple events or runs, with cumulative times determining overall rankings and champions.
-
D.
freestyle motocross competition series
A freestyle motocross competition series is an organized sequence of events where riders perform judged aerial tricks and stunts on motocross bikes to earn points, rankings, and titles over a season.
-
E.
freestyle skiing competition series
A freestyle skiing competition series is a recurring set of organized events in which athletes compete in various freestyle skiing disciplines, such as moguls, aerials, slopestyle, halfpipe, and big air, across multiple locations and dates.
- F. None of above. chosen
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_69f224a6d10481909290be1a00fc83b3 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:31 p.m.