Triple
T28446538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toronto 2015 Organizing Committee |
E715854
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | organizing committee for multi-sport event |
C6550
|
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: organizing committee for multi-sport event Context triple: [Toronto 2015 Organizing Committee, instanceOf, organizing committee for multi-sport event]
-
A.
sports governing committee
A sports governing committee is an organized body responsible for setting rules, overseeing competitions, and making policy decisions to regulate and promote a particular sport or group of sports.
-
B.
organizational committee
chosen
An organizational committee is a structured group of individuals formally appointed within an organization to plan, coordinate, and oversee specific functions, projects, or decision-making processes.
-
C.
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.
-
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 Games organizer
An Olympic Games organizer is responsible for planning, coordinating, and managing all aspects of hosting the Olympic Games, including logistics, venues, athletes, security, ceremonies, and compliance with International Olympic Committee 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_69efd6b44550819094ae991b553d9fc3 |
completed | April 27, 2026, 9:35 p.m. |
Created at: April 28, 2026, 1:49 a.m.