Triple
T16279651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Olympic Trials (track and field) |
E395231
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic qualifying event |
C19079
|
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: Olympic qualifying event Context triple: [U.S. Olympic Trials (track and field), instanceOf, Olympic qualifying event]
-
A.
Olympic qualifying tournament
chosen
An Olympic qualifying tournament is a competitive event or series of events through which athletes or teams earn the right to participate in the Olympic Games by meeting specific performance standards or rankings.
-
B.
Olympic sport
An Olympic sport is an athletic discipline recognized and governed by international federations and included in the Olympic Games program, where athletes from around the world compete under standardized rules.
-
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.
Olympic competition venue area
An Olympic competition venue area is a designated, secure space that includes the field of play and its immediate surroundings where official Olympic events are conducted according to sport-specific standards.
- 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_69d87f22c7248190a54c949738441e2e |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:05 a.m.