Triple
T38003076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CFL Players’ Association |
E948156
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | players’ association |
C3232
|
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: players’ association Context triple: [CFL Players’ Association, instanceOf, players’ association]
-
A.
players association
chosen
A players association is an organized group representing the collective interests, rights, and welfare of professional athletes within a particular sport or league.
-
B.
professional sports union
A professional sports union is an organized association of athletes in a professional league that collectively represents their interests in negotiations over wages, working conditions, benefits, and other employment-related matters with team owners and league management.
-
C.
professional sports league
A professional sports league is an organized association of teams or athletes that schedules and governs competitive events at the highest level of play, typically offering salaries, standardized rules, and commercialized entertainment.
-
D.
sports team collective
A sports team collective is a coordinated group of athletes, coaches, and supporting staff who work together under a shared identity to compete in organized sporting events and pursue common performance goals.
-
E.
sports labor system
The sports labor system is the structured network of rules, institutions, and relationships that govern how athletes’ work is organized, compensated, controlled, and negotiated within professional and amateur sports.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.