Triple
T17476565
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AHL All-Star Classic |
E425553
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Hockey League event |
C39279
|
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: American Hockey League event Context triple: [AHL All-Star Classic, instanceOf, American Hockey League event]
-
A.
National Hockey League event
A National Hockey League event is any scheduled or unscheduled occurrence officially organized, sanctioned, or recognized by the NHL, such as games, drafts, ceremonies, or media activities, involving league teams, players, officials, or stakeholders.
-
B.
Kontinental Hockey League event
A Kontinental Hockey League event is a professional ice hockey game or related official activity organized under the auspices of the KHL, involving its member teams, players, and regulations.
-
C.
United States Hockey League competition
A United States Hockey League competition is an organized ice hockey contest or series of contests held under the governance and rules of the USHL, typically involving junior-level teams competing for standings, titles, or championships.
-
D.
AHL season
An AHL season is the annual schedule of games, standings, and playoffs in the American Hockey League that determines team performance, player development, and the league champion.
-
E.
Western Hockey League competition
Western Hockey League competition represents any organized game, series, or tournament sanctioned by the WHL in which member teams contend under league rules to determine outcomes affecting standings, rankings, or championships.
- 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_69d889dbc2e88190b18ea6115e819258 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.