Triple
T1328096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canada Soccer |
E28376
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association football governing body |
C2641
|
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: association football governing body Context triple: [Canada Soccer, instanceOf, association football governing body]
-
A.
association football organization
An association football organization is an entity that governs, manages, or coordinates the playing, administration, and development of soccer competitions, clubs, and related activities within a defined scope or jurisdiction.
-
B.
football association
A football association is an organized governing body responsible for overseeing, regulating, and promoting the sport of football within a specific region or jurisdiction.
-
C.
association football club
An association football club is an organized team entity that competes in the sport of soccer under a common name, management, and identity, typically participating in official leagues and tournaments.
-
D.
football confederation
A football confederation is a regional governing body that organizes, regulates, and promotes association football competitions and development within a specific geographic area under the broader authority of FIFA.
-
E.
national football association
chosen
A national football association is the governing body responsible for organizing, regulating, and promoting football (soccer) within a specific country, including overseeing national teams, domestic leagues, and adherence to international rules.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.