Triple
T24346442
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Stanley Cup playoffs |
E613653
|
entity |
| Predicate | finalsWinningGoaltender |
P72636
|
FINISHED |
| Object | Mike Richter |
—
|
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: Mike Richter | Statement: [1994 Stanley Cup playoffs, finalsWinningGoaltender, Mike Richter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalsWinningGoaltender Context triple: [1994 Stanley Cup playoffs, finalsWinningGoaltender, Mike Richter]
-
A.
game7WinningGoaltender
Indicates the goaltender who earned the win in Game 7 of a playoff or series-deciding matchup.
-
B.
goaltenderChampion
chosen
Indicates that an entity serves as the championship-winning or title-holding goaltender for a team or competition.
-
C.
mostWinsGoaltenderWins
Indicates that the goaltender associated with this record holds the highest number of wins compared to all other goaltenders in the relevant context.
-
D.
StanleyCupWinningGoalScorer
Indicates the player who scored the decisive, championship-clinching goal in a given Stanley Cup Final series.
-
E.
topGoaltenderAward
Indicates that an entity has received an award recognizing them as the top-performing goaltender.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.