Triple
T25149486
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quickfire Challenge |
E630028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | recurring competition segment |
C4366
|
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: recurring competition segment Context triple: [Quickfire Challenge, instanceOf, recurring competition segment]
-
A.
competition section
chosen
A competition section is a designated part of an event, document, or platform that organizes, presents, and manages information, rules, and results related to specific contests or competitive activities.
-
B.
sports competition phase
A sports competition phase is a distinct, time-bounded segment of a sporting event or tournament (such as group stage, knockout round, or finals) characterized by specific rules, objectives, and progression criteria for participants.
-
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.
musical competition
A musical competition is an organized event where individuals or groups perform music before judges or an audience to be evaluated and ranked based on specific criteria.
-
E.
ritual competition
A ritual competition is a structured, often symbolic contest embedded in cultural or religious practice, where participants follow prescribed rules and performances to affirm social values, identities, or hierarchies.
- 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_69e2ff349e408190a6f4a5a66279f54d |
completed | April 18, 2026, 3:49 a.m. |
Created at: April 18, 2026, 6:30 a.m.