Triple
T30577083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1980 Stanley Cup Finals |
E778277
|
entity |
| Predicate | decidingGoalPeriod |
P169868
|
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: [1980 Stanley Cup Finals, decidingGoalPeriod, overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decidingGoalPeriod Context triple: [1980 Stanley Cup Finals, decidingGoalPeriod, overtime]
-
A.
decidingGoalMinute
Indicates the minute in a match when a goal is scored that ultimately decides the outcome (e.g., the winning or decisive goal).
-
B.
goalHorizon
Indicates the temporal or planning horizon within which a goal is intended to be pursued or achieved.
-
C.
goalType
Indicates the specific category or nature of a goal associated with an entity or action.
-
D.
initialGoal
Indicates that something represents the first or starting objective or target in a sequence of goals.
-
E.
goalSettingRole
Indicates a role in which an entity is responsible for defining, influencing, or managing goals for another entity or process.
- F. None of above. chosen
Provenance (4 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_69f2249f8c148190ae7eb3912cde112a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6893dc4e08190bd4fef06a9ba4247 |
completed | May 2, 2026, 11:31 p.m. |
| PD | Predicate disambiguation | batch_69f67e42d6688190b60e91d2c388c555 |
completed | May 2, 2026, 10:44 p.m. |
| PDg | Predicate description generation | batch_69f6827a7b9c8190ab13605aacc81df9 |
completed | May 2, 2026, 11:02 p.m. |
Created at: April 29, 2026, 8:22 p.m.