Triple
T25773408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIL Junior World Luge Championships |
E649080
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | junior sports competition |
C24736
|
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: junior sports competition Context triple: [FIL Junior World Luge Championships, instanceOf, junior sports competition]
-
A.
youth competition
chosen
A youth competition is an organized event where young individuals or teams compete in specific activities or disciplines to demonstrate their skills, talents, or knowledge, often within defined age categories.
-
B.
high school sports competition
A high school sports competition is an organized event where student athletes from one or more schools compete in structured athletic contests governed by standardized rules and regulations.
-
C.
under-20 basketball competition
An under-20 basketball competition is a structured tournament or league in which teams composed exclusively of players under the age of 20 compete under standardized basketball rules and age-eligibility regulations.
-
D.
youth football competition
A youth football competition is an organized sporting event or series of matches where young players or teams compete under age-specific rules and structures to develop skills and determine rankings or champions.
-
E.
under-16 basketball competition
An under-16 basketball competition is an organized sporting event where teams of players aged 16 and under compete in structured basketball games, typically following age-specific rules and development-focused guidelines.
- 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_69e7ab333b508190b6d708d8d9a328ed |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:32 a.m.