Triple
T11808715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uzooma Okeke |
E280814
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian Football League player |
C21537
|
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: Canadian Football League player Context triple: [Uzooma Okeke, instanceOf, Canadian Football League player]
-
A.
Canadian football player
chosen
A Canadian football player is an athlete who competes in Canadian football, typically in organized leagues such as the CFL or university conferences, following Canadian rules and field dimensions.
-
B.
Canadian football team
A Canadian football team is an organized group of players, coaches, and staff that competes in Canadian football competitions under a shared name, identity, and governance structure.
-
C.
American football player
An American football player is an athlete who participates in the sport of American football, executing specialized offensive, defensive, or special teams roles within an organized team structure.
-
D.
Canadian football coach
A Canadian football coach is an individual responsible for planning, directing, and managing the training, strategy, and in-game decisions of a Canadian football team within the rules and traditions of Canadian football.
-
E.
Canadian Football League tradition
The Canadian Football League tradition encompasses the enduring customs, rivalries, community rituals, and cultural practices that have developed around Canadian professional football, especially its distinctive rules, Grey Cup festivities, and regional fan identities.
- 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_69d6ab26aae88190b2489efcb2a24234 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:42 p.m.