Triple
T3901540
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 Stanley Cup Finals |
E90501
|
entity |
| Predicate | DetroitRedWingsStanleyCupDroughtEnded |
P52763
|
FINISHED |
| Object | 42 years |
—
|
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: 42 years | Statement: [1997 Stanley Cup Finals, DetroitRedWingsStanleyCupDroughtEnded, 42 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DetroitRedWingsStanleyCupDroughtEnded Context triple: [1997 Stanley Cup Finals, DetroitRedWingsStanleyCupDroughtEnded, 42 years]
-
A.
DetroitRedWingsConsecutiveCups
Indicates that the Detroit Red Wings won the Stanley Cup in consecutive seasons.
-
B.
StanleyCupWonWith
Indicates that a person or team won the Stanley Cup while being a member of or associated with a specific team.
-
C.
hasWonStanleyCup
Indicates that the subject (typically a team or player) has won at least one National Hockey League Stanley Cup championship.
-
D.
stanleyCupChampionWith
Indicates that one entity is the team or individual who won the Stanley Cup in association with the specified season, year, or context.
-
E.
stanleyCupWinYear
Indicates the specific year in which a given team won the Stanley Cup.
- 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_69aed95d315881908cbf1bf4a7215fbf |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aef1abe2dc81909c18aeae9b286898 |
completed | March 9, 2026, 4:13 p.m. |
| PD | Predicate disambiguation | batch_69aee75b5b808190a348a31b1325d3d0 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aef1aada308190821a3dfa6af170b3 |
completed | March 9, 2026, 4:13 p.m. |
Created at: March 9, 2026, 3:21 p.m.