Triple
T1602563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manchester Storm (ice hockey, former) |
E34426
|
entity |
| Predicate | playedHomeGamesAtIndoorArena |
P18826
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Manchester Storm (ice hockey, former), playedHomeGamesAtIndoorArena, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playedHomeGamesAtIndoorArena Context triple: [Manchester Storm (ice hockey, former), playedHomeGamesAtIndoorArena, yes]
-
A.
playsHomeGamesOn
chosen
Indicates that an entity regularly hosts its home games or matches at a specified location or venue.
-
B.
homeArenaAlternateName
Indicates that an entity’s home arena is known by an alternate or secondary name.
-
C.
playedAtStadium
Indicates that an event or game took place at, or was hosted in, a specific stadium.
-
D.
mainIndoorArena
Indicates that one entity serves as the primary indoor arena or main covered venue associated with another entity.
-
E.
primaryIndoorArena
Indicates that one entity serves as the main indoor arena or principal covered sports/entertainment venue for another entity.
- 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_69a885fea6a481909fe83ba6441f1774 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a95b02cd448190be8e3db9a5a7bac0 |
completed | March 5, 2026, 10:29 a.m. |
| PD | Predicate disambiguation | batch_69a907c1cad08190b9728dd557f39aa0 |
completed | March 5, 2026, 4:34 a.m. |
Created at: March 4, 2026, 7:28 p.m.