Triple
T13068908
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Hockey League |
E329401
|
entity |
| Predicate | usesIceRinkType |
P18571
|
FINISHED |
| Object | international-sized rink |
—
|
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 | Statement: [Austrian Hockey League, usesIceRinkType, international-sized rink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIceRinkType Context triple: [Austrian Hockey League, usesIceRinkType, international-sized rink]
-
A.
iceRinkType
chosen
Indicates the specific kind or category of an ice rink associated with an entity (e.g., indoor, outdoor, Olympic-sized).
-
B.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
C.
hasIceRinkDimensions
Indicates that an entity possesses or is characterized by specific ice rink measurements or size specifications.
-
D.
hasIceArena
Indicates that one entity possesses, contains, or includes an ice arena as a facility or feature.
-
E.
hasIcePads
Indicates that an entity is equipped with or contains ice pads, typically used for cooling or temperature regulation.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69d980ec8ba48190baf52c7823482680 |
completed | April 10, 2026, 10:59 p.m. |
| PD | Predicate disambiguation | batch_69d9803d46688190bac6b7d208f08d01 |
completed | April 10, 2026, 10:57 p.m. |
Created at: April 9, 2026, 9 p.m.