Triple
T7463281
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SHL |
E176302
|
entity |
| Predicate | usesIceRinkStandard |
P18571
|
FINISHED |
| Object | international-sized rink (IIHF standard) |
—
|
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: international-sized rink (IIHF standard) | Statement: [SHL, usesIceRinkStandard, international-sized rink (IIHF standard)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIceRinkStandard Context triple: [SHL, usesIceRinkStandard, international-sized rink (IIHF standard)]
-
A.
iceRinkType
chosen
Indicates the specific kind or category of an ice rink associated with an entity (e.g., indoor, outdoor, Olympic-sized).
-
B.
iceSurface
Indicates that something is located on, in contact with, or forming the surface of ice.
-
C.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
D.
hasIceArena
Indicates that one entity possesses, contains, or includes an ice arena as a facility or feature.
-
E.
hasIceSurface
Indicates that an entity possesses or is characterized by a surface composed primarily of ice.
- 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_69c69f21632481908bf83f6c6da897e3 |
completed | March 27, 2026, 3:15 p.m. |
| NER | Named-entity recognition | batch_69c6f3d80ae08190ba383066cf0cb2ce |
completed | March 27, 2026, 9:17 p.m. |
| PD | Predicate disambiguation | batch_69c6f03bad9c8190bdd5abb86d37df47 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:39 p.m.