Triple
T24284550
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4 × 100 metres relay |
E605635
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | track and field relay event |
C48643
|
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: track and field relay event Context triple: [4 × 100 metres relay, instanceOf, track and field relay event]
-
A.
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.
-
B.
international track and field competition
An international track and field competition is a globally organized sporting event where athletes from multiple countries compete in a range of running, jumping, and throwing disciplines under standardized rules.
-
C.
swimming relay event
A swimming relay event is a competitive race in which teams of swimmers take turns completing equal segments of the total distance in a specified stroke order, with each swimmer starting only after the previous teammate finishes.
-
D.
combined track and field event
A combined track and field event is a competition in which athletes contest multiple track and field disciplines over one or more days, with performances in each contributing to an overall score.
-
E.
short track speed skating relay event
A short track speed skating relay event is a team race on an oval ice track where skaters take turns completing multiple laps at high speed, exchanging through pushes rather than physical batons to collectively cover a set distance in the fastest time.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:08 a.m.