Triple
T22286752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | International Professional Hockey League |
E550882
|
entity |
| Predicate | playedInArenaType |
P23143
|
FINISHED |
| Object | indoor ice rinks |
—
|
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: indoor ice rinks | Statement: [International Professional Hockey League, playedInArenaType, indoor ice rinks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedInArenaType Context triple: [International Professional Hockey League, playedInArenaType, indoor ice rinks]
-
A.
playedInArena
Indicates that an entity (typically a performer or team) participated in an event that took place within a specific arena.
-
B.
playsInArenaLocatedIn
Indicates that an entity performs or participates in events within an arena that is geographically located in a specified place.
-
C.
playsInIndoorArena
Indicates that an entity participates or performs in an arena that is located indoors.
-
D.
arenaType
chosen
Indicates the specific kind or category of arena associated with an entity or event.
-
E.
playedInTournament
Indicates that an entity participated as a competitor or player in a specific tournament.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15607d9948190b4b8e9cd7fa4d390 |
completed | April 29, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69e72ff0363081909f794d19c8a64837 |
completed | April 21, 2026, 8:06 a.m. |
Created at: April 16, 2026, 8:40 p.m.