Triple
T19819275
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1995 Stanley Cup Finals |
E476142
|
entity |
| Predicate | Game4Score |
P137444
|
FINISHED |
| Object | New Jersey Devils 5–2 Detroit Red Wings |
—
|
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: New Jersey Devils 5–2 Detroit Red Wings | Statement: [1995 Stanley Cup Finals, Game4Score, New Jersey Devils 5–2 Detroit Red Wings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: Game4Score Context triple: [1995 Stanley Cup Finals, Game4Score, New Jersey Devils 5–2 Detroit Red Wings]
-
A.
Game2Winner
Indicates that the referenced entity is the winner of the second game in a series or sequence of games.
-
B.
game4City
Indicates that a game is associated with, played in, or represents a particular city.
-
C.
isPartOfScoreBy
Indicates that something constitutes a component or segment within a larger score or musical composition.
-
D.
game4Save
Indicates a relationship where a game is being saved or a save action/state is associated with a particular game instance.
-
E.
Game7Save
Indicates a game situation where a player or team successfully preserves a lead in a decisive seventh game, securing the win under high-pressure, series-deciding conditions.
- 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_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. |
| PDg | Predicate description generation | batch_69e532bcf41c8190b685b5adf46a60fc |
completed | April 19, 2026, 7:53 p.m. |
Created at: April 10, 2026, 1:50 p.m.