Triple
T25096982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Luleå HF |
E628613
|
entity |
| Predicate | hasIceHockeyDiscipline |
P116823
|
FINISHED |
| Object | men's 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: men's ice hockey | Statement: [Luleå HF, hasIceHockeyDiscipline, men's ice hockey]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasIceHockeyDiscipline Context triple: [Luleå HF, hasIceHockeyDiscipline, men's ice hockey]
-
A.
hasIceHockeyCapacity
Indicates that an entity is capable of hosting or accommodating ice hockey activities, such as games or practices.
-
B.
hasIceArena
Indicates that one entity possesses, contains, or includes an ice arena as a facility or feature.
-
C.
skatingDiscipline
chosen
Indicates the specific type or category of skating discipline associated with an entity (e.g., figure, speed, ice dance).
-
D.
hasOlympicDiscipline
Indicates that an entity (typically a sport) includes or is associated with a specific discipline as recognized in the Olympic Games.
-
E.
WorldCupDiscipline
Indicates a disciplinary action (such as a card, suspension, or sanction) imposed on an entity in the context of a FIFA World Cup competition.
- 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f464b9651481908d4d7584717f5c59 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:25 a.m.