Triple
T16788234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diamond League |
E408034
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | annual athletics competition series |
C36803
|
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: annual athletics competition series Context triple: [Diamond League, instanceOf, annual athletics competition series]
-
A.
annual sporting event
An annual sporting event is a recurring, organized athletic competition held once each year, typically featuring established rules, participants, and traditions that attract spectators and media attention.
-
B.
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.
-
C.
international sporting event series
chosen
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.
-
D.
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.
-
E.
intercollegiate athletic events
Intercollegiate athletic events are organized sports competitions in which teams or individuals representing different colleges or universities compete under established rules and governing bodies.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.