Triple
T2605375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melbourne 2006 Commonwealth Games Corporation |
E58645
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports event organising body |
C5629
|
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: sports event organising body Context triple: [Melbourne 2006 Commonwealth Games Corporation, instanceOf, sports event organising body]
-
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.
sports administration organization
chosen
A sports administration organization is an entity responsible for governing, regulating, and managing the operations, policies, and development of sports activities, leagues, or associations within its jurisdiction.
-
C.
sports management company
A sports management company is an organization that represents and supports athletes or sports entities by handling contracts, marketing, endorsements, career planning, and related business affairs.
-
D.
sports society
A sports society is an organized group or club that brings people together to participate in, promote, and enjoy sports-related activities, events, and community engagement.
-
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_69ab4ac3523881909679750c9f8c2dec |
completed | March 6, 2026, 9:44 p.m. |
Created at: March 6, 2026, 9:49 p.m.