Triple
T30204166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederation of African Football regional unions |
E767864
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | CAF sub-confederation |
C1287
|
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: CAF sub-confederation Context triple: [Confederation of African Football regional unions, instanceOf, CAF sub-confederation]
-
A.
football confederation
chosen
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.
-
B.
CAF Confederation Cup season
A CAF Confederation Cup season is the annual cycle of the Confederation of African Football’s secondary club competition, encompassing all qualifying rounds, group stages, and knockout matches leading to the crowning of the continental champion.
-
C.
ISAF regional command
ISAF regional command is a military organizational unit responsible for planning, coordinating, and overseeing International Security Assistance Force operations within a designated geographic region.
-
D.
NAFO division
A NAFO division is a specific geographic subarea within the Northwest Atlantic Fisheries Organization’s regulatory area used to manage and report marine fisheries resources.
-
E.
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.
- 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_69f2247eb0848190b4032f302d39c0d9 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:31 p.m.