Triple
T33313926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA normalization committee intervention in 2016 |
E852960
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FIFA normalization committee |
C59189
|
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: FIFA normalization committee Context triple: [FIFA normalization committee intervention in 2016, instanceOf, FIFA normalization committee]
-
A.
FIFA Congress
The FIFA Congress is the supreme legislative and decision-making body of FIFA, comprising representatives from all member associations who convene to set policies, elect officials, and amend regulations governing international football.
-
B.
FIFA initiative
A FIFA initiative is an organized program or project launched by FIFA to develop, regulate, or promote football globally in areas such as governance, infrastructure, competitions, or social impact.
-
C.
FIFA presidential election
The FIFA presidential election is the formal process by which member associations of football’s global governing body vote to choose the organization’s president for a defined term.
-
D.
division of FIFA
A division of FIFA is an organizational unit within the Fédération Internationale de Football Association responsible for managing specific functional areas such as competitions, governance, development, or commercial operations in global football.
-
E.
FIFA trigramme
A FIFA trigramme is the unique three-letter code assigned by FIFA to identify a national football association or its representative teams in official competitions and records.
- F. None of above. chosen
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.