Triple
T19819308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Stanley Cup Finals |
E476143
|
entity |
| Predicate | finalClinchingGame |
P121297
|
FINISHED |
| Object | Game 6 |
—
|
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: Game 6 | Statement: [2008 Stanley Cup Finals, finalClinchingGame, Game 6]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalClinchingGame Context triple: [2008 Stanley Cup Finals, finalClinchingGame, Game 6]
-
A.
clinchedInGame
Indicates that a team or player secured a decisive outcome (such as winning a series, title, or advancement) specifically in that particular game.
-
B.
finalGameLeague
Indicates that a game is the concluding or championship match within a particular league or league season.
-
C.
finalManOfTheMatch
Indicates that the referenced person was chosen as the ultimate or concluding Man of the Match for a particular game or series.
-
D.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
E.
finalGameNumber
chosen
Indicates the specific number assigned to the last or concluding game in a series, season, or sequence of games.
- 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_69d8e51c7c188190b926f3a2a7b5f881 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e654fc8b94819095fd5240f33b6713 |
completed | April 20, 2026, 4:31 p.m. |
| PD | Predicate disambiguation | batch_69e5305bda388190a23b7191768107b1 |
completed | April 19, 2026, 7:43 p.m. |
Created at: April 10, 2026, 1:50 p.m.