Triple
T12337852
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neil McEvoy |
E294137
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Canadian football executive |
C31319
|
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 executive Context triple: [Neil McEvoy, instanceOf, Canadian football executive]
-
A.
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.
-
B.
American football executive
An American football executive is a high-level professional responsible for overseeing the strategic, financial, and operational aspects of an American football organization, including player personnel decisions, coaching hires, and long-term team development.
-
C.
Canadian football player
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.
-
D.
Canadian football league
The Canadian Football League is a professional sports organization that oversees and operates teams competing in Canadian-style gridiron football across Canada.
-
E.
Australian rules football administrator
An Australian rules football administrator is a professional responsible for managing, organizing, and overseeing the operations, governance, and strategic development of Australian rules football at club, league, or national levels.
- F. None of above. chosen
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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:53 p.m.