Triple
T15457863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ice Arena Wales |
E371817
|
entity |
| Predicate | hasSecondaryRinkType |
P18571
|
FINISHED |
| Object | practice ice 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: practice ice rink | Statement: [Ice Arena Wales, hasSecondaryRinkType, practice ice rink]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryRinkType Context triple: [Ice Arena Wales, hasSecondaryRinkType, practice ice rink]
-
A.
hasSecondaryHall
Indicates that an entity is associated with or contains an additional, subordinate hall beyond its primary hall.
-
B.
playsOnRinkType
Indicates that an entity participates in a game or activity on a specific type of rink surface or rink configuration.
-
C.
iceRinkType
chosen
Indicates the specific kind or category of an ice rink associated with an entity (e.g., indoor, outdoor, Olympic-sized).
-
D.
hasSecondaryHallCapacity
Indicates that an entity possesses a specified capacity for a secondary hall or auxiliary event space.
-
E.
hasSecondary
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03f1623f0819086f6fc2bfd536609 |
completed | April 16, 2026, 1:44 a.m. |
| PD | Predicate disambiguation | batch_69ded284bd008190b31c53b4f1cebadd |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:31 a.m.