Triple
T31673671
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOCOG |
E808339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Olympic Games organizing committee |
C7307
|
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: Olympic Games organizing committee Context triple: [SOCOG, instanceOf, Olympic Games organizing committee]
-
A.
Olympic Games organizer
chosen
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.
-
B.
Olympic legacy organization
An Olympic legacy organization is an entity dedicated to preserving, managing, and enhancing the long-term social, economic, and environmental benefits of hosting the Olympic Games for the host city, region, and nation.
-
C.
National Olympic Committee
A National Olympic Committee is the organization recognized by the International Olympic Committee as responsible for developing, promoting, and overseeing Olympic sports and athletes within a specific country or territory.
-
D.
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.
-
E.
Eurasian sports organization
A Eurasian sports organization is an entity that governs, promotes, and coordinates athletic activities, competitions, and development programs across countries spanning Europe and Asia.
- 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_69f348dcf5d48190ac25b1365ae717a8 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:02 p.m.