Triple
T22573106
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The IRONMAN Group |
E544324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | triathlon organizer |
C34831
|
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: triathlon organizer Context triple: [The IRONMAN Group, instanceOf, triathlon organizer]
-
A.
race organizer
chosen
A race organizer is an entity responsible for planning, coordinating, and managing all logistical, regulatory, and participant-related aspects of a race event.
-
B.
motorsport organizer
A motorsport organizer is an entity responsible for planning, coordinating, and overseeing competitive racing events, ensuring regulatory compliance, safety, logistics, and participant management.
-
C.
triathlon race
A triathlon race is a multi-discipline endurance event in which athletes consecutively complete swimming, cycling, and running segments over specified distances, often with timed transitions between each discipline.
-
D.
cooperative organizer
A cooperative organizer is an individual or system that coordinates people, resources, and processes to collaboratively plan, manage, and execute shared goals within a cooperative structure.
-
E.
professional golf tour organizer
A professional golf tour organizer is responsible for planning, coordinating, and managing all aspects of professional golf tournaments and tours, including scheduling events, securing venues and sponsors, handling player logistics, and ensuring compliance with governing bodies and regulations.
- 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_69e11e30d05481909df915354c89f0d6 |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:53 p.m.