Triple
T20562950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997–98 Detroit Red Wings |
E504889
|
entity |
| Predicate | StanleyCupFinalClinchingGameScore |
P36440
|
FINISHED |
| Object | 4–1 |
—
|
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: 4–1 | Statement: [1997–98 Detroit Red Wings, StanleyCupFinalClinchingGameScore, 4–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StanleyCupFinalClinchingGameScore Context triple: [1997–98 Detroit Red Wings, StanleyCupFinalClinchingGameScore, 4–1]
-
A.
finalNHLGame
Indicates that an NHL game is the last or concluding game in a specified series, season, or career context.
-
B.
StanleyCupChallengeScore
Indicates a scoring relationship in which an entity records or is assigned a score specifically for a Stanley Cup challenge or competition.
-
C.
StanleyCupFinalsGames
Indicates a relationship where specific games are identified as belonging to the Stanley Cup Finals series in a given season.
-
D.
StanleyCupFinalsSeriesResult
Indicates the outcome of a Stanley Cup Finals series, specifying which team won and by what series score.
-
E.
championshipGameScore
chosen
Indicates the final score achieved by each participant in a championship game.
- 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_69e0b4b6587c8190aee63dc7cff244ea |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6a79f906c819081163de9649ccb17 |
completed | April 20, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69e59ff0116c8190a163ff28ed01430a |
completed | April 20, 2026, 3:39 a.m. |
Created at: April 16, 2026, 11:39 a.m.