Triple
T10415753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1953–54 NHL season |
E245510
|
entity |
| Predicate | StanleyCupWinningGoalGame |
P2220
|
FINISHED |
| Object | Game 7 overtime |
—
|
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: Game 7 overtime | Statement: [1953–54 NHL season, StanleyCupWinningGoalGame, Game 7 overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StanleyCupWinningGoalGame Context triple: [1953–54 NHL season, StanleyCupWinningGoalGame, Game 7 overtime]
-
A.
StanleyCupWinningGoalScorer
Indicates the player who scored the decisive, championship-clinching goal in a given Stanley Cup Final series.
-
B.
scoredGameWinningGoal
chosen
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
C.
StanleyCupFinalsMVP
Indicates that the subject was selected as the Most Valuable Player (MVP) of the Stanley Cup Finals in a given season.
-
D.
losingGoaltender
Indicates that a particular goaltender is the one who was in net for the team that lost the game.
-
E.
goldenGoalRuleUsed
Indicates that the outcome of a match or competition was determined using the golden goal rule, where the first score in extra time immediately ends the game.
- 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_69d381be340c8190b05998703d42d224 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea108fec8190819423630888fa2b |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb6f160819090040644a12395ec |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:10 p.m.