Triple
T16040209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Stanley Cup Finals |
E389073
|
entity |
| Predicate | seriesWinningGoalPeriod |
P51805
|
FINISHED |
| Object | second 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: second overtime | Statement: [2000 Stanley Cup Finals, seriesWinningGoalPeriod, second overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesWinningGoalPeriod Context triple: [2000 Stanley Cup Finals, seriesWinningGoalPeriod, second overtime]
-
A.
clinchingGoalPeriod
chosen
Indicates the time period or segment of play during which the decisive, game-clinching goal was scored.
-
B.
game7WinningGoalPeriod
Indicates the period of play in which the winning goal was scored in Game 7 of a series or matchup.
-
C.
scoredGameWinningGoal
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
D.
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.
-
E.
titleWinningGoalScorer
Indicates the player who scored the decisive goal that secured a title or championship in a competition.
- 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_69d86dada3808190825d5f80d72fbe88 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1ff63edb0819092cbb671967bbdcd |
completed | April 17, 2026, 9:37 a.m. |
| PD | Predicate disambiguation | batch_69e1826f34c081908005bb736f1c485d |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 4:56 a.m.