Triple
T23776420
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | FIFA confederations |
E587687
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | association football organizational structure |
C3200
|
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 organizational structure Context triple: [FIFA confederations, instanceOf, association football organizational structure]
-
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.
association football league system
An association football league system is a hierarchical structure of interconnected football leagues, typically organized by promotion and relegation, that determines the competitive levels and progression of clubs within a country or region.
-
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 law-making body
A football law-making body is an authoritative organization responsible for creating, interpreting, and updating the official rules and regulations that govern how football is played worldwide.
-
E.
football association
chosen
A football association is an organized governing body responsible for overseeing, regulating, and promoting the sport of football within a specific region or 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_69e2490d245881909028226a1393d624 |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 7:16 p.m.