Triple
T13402216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bill McCreary |
E319858
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | National Hockey League official |
C23984
|
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: National Hockey League official Context triple: [Bill McCreary, instanceOf, National Hockey League official]
-
A.
National Hockey League executive
A National Hockey League executive is a high-level decision-maker responsible for overseeing league or team operations, including business strategy, governance, and competitive integrity within the NHL.
-
B.
NHL administrative body
The NHL administrative body is the central organizational authority responsible for governing league operations, enforcing rules and policies, managing business affairs, and coordinating activities among teams, players, and stakeholders within the National Hockey League.
-
C.
ice hockey official
chosen
An ice hockey official is a trained individual responsible for enforcing the rules, ensuring fair play, and maintaining game flow and safety during an ice hockey match.
-
D.
National Hockey League coach
A National Hockey League coach is a professional responsible for directing an NHL team’s strategy, player development, in-game decisions, and overall performance throughout the season and playoffs.
-
E.
National Hockey League conference
A National Hockey League conference is a major organizational division of NHL teams, grouped primarily by geography, that determines regular-season scheduling and playoff qualification structure.
- 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_69d806b943cc8190b6af624d385d7e12 |
completed | April 9, 2026, 8:06 p.m. |
Created at: April 9, 2026, 9:34 p.m.