Triple
T16144463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1964 Stanley Cup playoffs |
E391741
|
entity |
| Predicate | finalGameNumber |
P121297
|
FINISHED |
| Object | Game 7 |
—
|
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 7 | Statement: [1964 Stanley Cup playoffs, finalGameNumber, Game 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGameNumber Context triple: [1964 Stanley Cup playoffs, finalGameNumber, Game 7]
-
A.
winningGameNumber
Indicates the specific game number in a series or sequence that results in a win for a given participant or side.
-
B.
finalGameLeague
Indicates that a game is the concluding or championship match within a particular league or league season.
-
C.
finalHomeGameResult
Indicates the outcome of an entity’s last home game in a given context or season.
-
D.
finalScore
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
E.
finalLeague
Indicates the league or competition in which an entity ultimately ends up or is officially classified, typically after all stages or transitions are complete.
- 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_69d87f1c65e48190aa2b4c472e9bafc4 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21d92b0408190a010bd8e5193aa36 |
completed | April 17, 2026, 11:46 a.m. |
| PD | Predicate disambiguation | batch_69e182885bc08190822ae7e8a4b8ac1f |
completed | April 17, 2026, 12:44 a.m. |
| PDg | Predicate description generation | batch_69e1835b64948190ae1d2a9d4cc64acf |
completed | April 17, 2026, 12:48 a.m. |
Created at: April 10, 2026, 5:01 a.m.