Triple
T11141444
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | decathlon |
E263563
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | combined track and field event |
C29278
|
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: combined track and field event Context triple: [decathlon, instanceOf, combined track and field event]
-
A.
college track and field competition
A college track and field competition is an organized athletic meet where collegiate athletes represent their institutions in a variety of running, jumping, and throwing events under standardized rules and scoring.
-
B.
track and field relay meet
A track and field relay meet is a competitive event where teams of runners race in sequential legs, passing a baton within designated exchange zones to achieve the fastest overall time.
-
C.
college track and field championship
A college track and field championship is a competitive athletic event where collegiate teams and athletes contest a series of track races and field events to determine individual and team titles at a conference, regional, or national level.
-
D.
multi-sport event
A multi-sport event is a large-scale organized competition in which athletes from various regions or groups compete across multiple different sports within a unified program and schedule.
-
E.
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.
- 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_69d6aa9c0ba08190bbd19c217489b755 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:28 p.m.