Triple
T3157359
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIFK Helsinki |
E66015
|
entity |
| Predicate | playsIceHockeyCode |
P46676
|
FINISHED |
| Object | ice hockey |
—
|
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: ice hockey | Statement: [HIFK Helsinki, playsIceHockeyCode, ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playsIceHockeyCode Context triple: [HIFK Helsinki, playsIceHockeyCode, ice hockey]
-
A.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
B.
IIHFCode
Indicates the standardized code assigned by the International Ice Hockey Federation (IIHF) to identify a national ice hockey association or team.
-
C.
hasIceArena
Indicates that one entity possesses, contains, or includes an ice arena as a facility or feature.
-
D.
playedCollegeHockeyFor
Indicates that a person was a member of and competed for a particular college or university’s ice hockey team.
-
E.
iceHockeyAffiliation
Indicates an affiliation relationship between an entity and an ice hockey organization, such as a team, league, or club.
- F. None of above. chosen
Provenance (4 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_69ad85850c1481908a9e9c6242238de2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada5ec0da88190a83f3448ac76e98e |
completed | March 8, 2026, 4:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfbf0348190952a6bca8fc5fed1 |
completed | March 8, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69ada1e4f7288190a80a1672e458132d |
completed | March 8, 2026, 4:20 p.m. |
Created at: March 8, 2026, 3:05 p.m.