Triple
T16040213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000 Stanley Cup Finals |
E389073
|
entity |
| Predicate | game5OvertimeCount |
P114842
|
FINISHED |
| Object | three overtimes |
—
|
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: three overtimes | Statement: [2000 Stanley Cup Finals, game5OvertimeCount, three overtimes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: game5OvertimeCount Context triple: [2000 Stanley Cup Finals, game5OvertimeCount, three overtimes]
-
A.
longestGameOvertimes
chosen
Indicates the number of overtime periods played in the longest game (by duration or overtime count) within a given context.
-
B.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
C.
pointsForOvertimeOrShootoutLoss
Indicates the number of points awarded to a team specifically for losing a game in overtime or a shootout.
-
D.
featuresExtraInningGames
Indicates that the subject includes or contains games that extend beyond the standard number of innings (extra-inning games).
-
E.
goalsInExtraTime
Indicates that the related entity scored goals specifically during the extra time period of a match, beyond regular playing time.
- 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.