Triple
T15264760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL Centennial Classic |
E364869
|
entity |
| Predicate | gameWinningGoalPeriod |
P51805
|
FINISHED |
| Object | 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: overtime | Statement: [NHL Centennial Classic, gameWinningGoalPeriod, overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: gameWinningGoalPeriod Context triple: [NHL Centennial Classic, gameWinningGoalPeriod, overtime]
-
A.
game7WinningGoalPeriod
Indicates the period of play in which the winning goal was scored in Game 7 of a series or matchup.
-
B.
clinchingGoalPeriod
chosen
Indicates the time period or segment of play during which the decisive, game-clinching goal was scored.
-
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.
gameWinningScoreBy
Indicates that a particular score is the decisive amount by which a game is won by an 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00851c5b88190a296b6a105d3ee30 |
completed | April 15, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69deca8d1bd48190a4b94f29b425e335 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:14 a.m.