Triple
T25066301
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Stanley Cup Finals |
E627791
|
entity |
| Predicate | championStanleyCupsConsecutive |
P79545
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [2017 Stanley Cup Finals, championStanleyCupsConsecutive, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championStanleyCupsConsecutive Context triple: [2017 Stanley Cup Finals, championStanleyCupsConsecutive, 2]
-
A.
consecutiveStanleyCups
chosen
Indicates that a team has won Stanley Cup championships in back-to-back seasons without interruption.
-
B.
teamAchievedFourConsecutiveStanleyCupsWith
Indicates that a team, together with a specified coach, roster, or organization, achieved four Stanley Cup championships in consecutive seasons.
-
C.
StanleyCupWinnerSeriesWins
Indicates the number of games won in the championship series by the team that wins the Stanley Cup.
-
D.
mostStanleyCupsInNHL
Indicates having won the greatest number of Stanley Cup championships in the history of the NHL compared to all other entities.
-
E.
StanleyCupWinningSeasons
Indicates the seasons in which a team won the Stanley Cup championship.
- 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_69e2ff2d71dc8190b4758e57d643cbe4 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f4599e14688190aa19833f62ffb283 |
completed | May 1, 2026, 7:43 a.m. |
| PD | Predicate disambiguation | batch_69f44d77f6e88190a4643ab2cbef567b |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:10 a.m.