Triple
T33313925
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA normalization committee intervention in 2016 |
E852960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports governance intervention |
C5768
|
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 governance intervention Context triple: [FIFA normalization committee intervention in 2016, instanceOf, sports governance intervention]
-
A.
sports governance role
A sports governance role is a position responsible for overseeing the rules, policies, integrity, and strategic direction of sports organizations or competitions.
-
B.
sports governing committee
chosen
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.
-
C.
sports governance meeting
A sports governance meeting is a formal gathering of stakeholders responsible for setting policies, making strategic decisions, and overseeing the rules, ethics, and administration of sports organizations or competitions.
-
D.
international sports governance document
An international sports governance document is a formal, authoritative text that defines the rules, structures, and decision-making processes guiding the organization, regulation, and conduct of sports across multiple countries.
-
E.
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.
- 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_69f349679fd8819093b9b40e989440e3 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:33 a.m.