Triple
T19905447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Team Canada (assistant coach) |
E478401
|
entity |
| Predicate | iceHockeyCode |
P126120
|
FINISHED |
| Object | IIHF rules |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: IIHF rules | Statement: [Team Canada (assistant coach), iceHockeyCode, IIHF rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: iceHockeyCode Context triple: [Team Canada (assistant coach), iceHockeyCode, IIHF rules]
-
A.
playsIceHockeyCode
Indicates that one entity participates in ice hockey under the specific code, ruleset, or organizational classification represented by the other entity.
-
B.
IIHFCode
Indicates the standardized code assigned by the International Ice Hockey Federation (IIHF) to identify a national ice hockey association or team.
-
C.
iceHockeyCharacteristic
Indicates a characteristic, feature, or attribute specifically associated with the sport of ice hockey.
-
D.
iceHockeyFormat
chosen
Indicates that the subject is associated with or uses a particular format, structure, or rule set specific to ice hockey.
-
E.
iceHockeyStatus
Indicates the current role, condition, or game-related state of an entity within the context of ice hockey.
- F. None of above.
Provenance (3 batches)
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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65946916881909c3f52208c07aa64 |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.