Triple
T23030337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA Club World Cup final ceremony |
E573438
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FIFA event |
C46323
|
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 event Context triple: [FIFA Club World Cup final ceremony, instanceOf, FIFA event]
-
A.
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.
-
B.
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.
-
C.
FIFA World Cup campaign
A FIFA World Cup campaign is the organized, multi-stage effort by a national football team and its association to qualify for, prepare for, and compete in a specific edition of the FIFA World Cup, encompassing strategic planning, player selection, training, matches, and promotional activities.
-
D.
FIFA property
chosen
A FIFA property is any event, competition, brand element, or commercial asset owned, organized, sanctioned, or otherwise controlled by FIFA, including its tournaments, trademarks, media rights, and associated intellectual property.
-
E.
FIFA World Cup tradition
A FIFA World Cup tradition is a recurring practice, ritual, or custom associated with the tournament that reflects its history, culture, and global fan experience.
- 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_69e245b911188190bc3d96326c847969 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:53 p.m.