Triple
T1343526
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lokomotiv Yaroslavl |
E28518
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | professional ice hockey club |
C130
|
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: professional ice hockey club Context triple: [Lokomotiv Yaroslavl, instanceOf, professional ice hockey club]
-
A.
professional ice hockey team
chosen
A professional ice hockey team is an organized group of elite players, coaches, and staff that competes in sanctioned ice hockey leagues and tournaments as a commercial sports franchise.
-
B.
major junior ice hockey team
A major junior ice hockey team is a high-level, youth-focused competitive hockey club, typically composed of players aged 16–20, that competes in a top-tier junior league and serves as a primary development path toward professional play.
-
C.
NHL team
An NHL team is a professional ice hockey organization that competes in the National Hockey League, consisting of players, coaches, and staff representing a specific city or region.
-
D.
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.
-
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_69a49854eb3481908c7d56b2e449a290 |
completed | March 1, 2026, 7:49 p.m. |
Created at: March 1, 2026, 7:56 p.m.