Triple
T3796706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 Stanley Cup Finals |
E91586
|
entity |
| Predicate | clinchingGoalType |
P16644
|
FINISHED |
| Object | triple-overtime goal |
—
|
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: triple-overtime goal | Statement: [1999 Stanley Cup Finals, clinchingGoalType, triple-overtime goal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinchingGoalType Context triple: [1999 Stanley Cup Finals, clinchingGoalType, triple-overtime goal]
-
A.
clinchingHomeRunType
Indicates the specific type or category of a home run that clinches or decisively secures a game, series, or title.
-
B.
clinchingPlayDescription
chosen
Indicates the descriptive text of the specific play or action that secured a decisive victory or outcome in a game or competition.
-
C.
ownGoalBy
Indicates that a goal was accidentally scored against a team by the specified player (i.e., the player scored an own goal).
-
D.
scoredGameWinningGoal
Indicates that an entity scored the decisive goal that determined the final victory in a game.
-
E.
clinchedBy
Indicates that a particular outcome, title, or achievement has been definitively secured or guaranteed by a specific 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_69aed96354f48190a768966d6bd19b04 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aeecefa3608190a7a20ed6df6a64b2 |
completed | March 9, 2026, 3:53 p.m. |
| PD | Predicate disambiguation | batch_69aee743c8d08190a9f9c97b836bd703 |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:15 p.m.