Triple
T6899286
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glasgow 2014 Organising Committee |
E159452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports event organising committee |
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: sports event organising committee Context triple: [Glasgow 2014 Organising Committee, instanceOf, sports event organising committee]
-
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
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.
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.
-
D.
sports officiating organization
A sports officiating organization is an entity that recruits, trains, assigns, and oversees referees and officials to ensure fair and consistent enforcement of rules in athletic competitions.
-
E.
sports organization collective
A sports organization collective is a coordinated group of sports entities—such as teams, clubs, leagues, or associations—that collaborate under shared governance, resources, or objectives to promote, manage, and develop athletic activities.
- 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_69c6883822e0819091e321526f20ae0a |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:24 p.m.