Triple
T34910154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1989 Stanley Cup playoffs |
E1006841
|
entity |
| Predicate | finalsHomeArenaRunnerUp |
P48390
|
FINISHED |
| Object | Montreal Forum |
—
|
NE NERFINISHED |
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: Montreal Forum | Statement: [1989 Stanley Cup playoffs, finalsHomeArenaRunnerUp, Montreal Forum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalsHomeArenaRunnerUp Context triple: [1989 Stanley Cup playoffs, finalsHomeArenaRunnerUp, Montreal Forum]
-
A.
homeArenaOfRunnerUpTeam
chosen
Indicates the venue that serves as the home arena for the team that finished as runner-up in a competition or event.
-
B.
finalsAppearanceForRunnerUpFranchiseNumber
Indicates the number of times a franchise has appeared in the finals in seasons where it finished as the runner-up.
-
C.
quarterFinalHostStadium
Indicates that a particular stadium is the venue where a quarter-final match is hosted.
-
D.
playoffVenue
Indicates the location or facility where a playoff game or playoff series is held.
-
E.
runnerUpHomeArena
Indicates the home arena associated with the entity that finished as runner-up in a given competition or event.
- 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_69f76dc1b4a081909b4c6e4d8ec0aa2d |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fe7eb4b8348190bb19d35766189ed4 |
completed | May 9, 2026, 12:24 a.m. |
| PD | Predicate disambiguation | batch_69fe7c35d2148190ab952e54feda1e76 |
completed | May 9, 2026, 12:13 a.m. |
Created at: May 3, 2026, 4 p.m.