Triple
T1332051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | League1 Ontario |
E28664
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | semi-professional sports league |
C1575
|
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: semi-professional sports league Context triple: [League1 Ontario, instanceOf, semi-professional sports league]
-
A.
amateur sports league
chosen
An amateur sports league is an organized association of non-professional teams or individuals who regularly compete under shared rules, schedules, and governance for recreation and community engagement rather than financial gain.
-
B.
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.
-
C.
minor league
A minor league is a lower-tier professional sports organization where athletes develop their skills and gain experience before potentially advancing to a major league.
-
D.
professional basketball league
A professional basketball league is an organized competition in which franchised or club teams of paid, elite basketball players play a structured season of games culminating in playoffs and a championship.
-
E.
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.
- 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_69a498561a508190a3e1bc137c2b866a |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:55 p.m.