Triple
T24346447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Stanley Cup playoffs |
E613653
|
entity |
| Predicate | finalsGame7Score |
P32584
|
FINISHED |
| Object | New York Rangers 3–2 Vancouver Canucks |
—
|
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 York Rangers 3–2 Vancouver Canucks | Statement: [1994 Stanley Cup playoffs, finalsGame7Score, New York Rangers 3–2 Vancouver Canucks]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalsGame7Score Context triple: [1994 Stanley Cup playoffs, finalsGame7Score, New York Rangers 3–2 Vancouver Canucks]
-
A.
worldSeriesGame7FinalScore
Indicates the final score outcome of the decisive Game 7 in a World Series matchup between two teams.
-
B.
game7Score
chosen
Indicates the final score or outcome of a decisive seventh game in a series between competitors.
-
C.
game6FinalScore
Indicates the final score achieved in the sixth game of a series or sequence of games.
-
D.
game7WinningRunScoredBy
Indicates which player scored the run that ultimately decided the outcome in Game 7.
-
E.
game5FinalScore
Indicates the final score outcome of a specific game (game 5) in a series or match.
- 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_69e2d7ddd29481909e7f539a6072bd71 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f2932978b88190afc441a3d4805e5f |
completed | April 29, 2026, 11:24 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:58 a.m.