Triple
T37384778
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stanley Cup 2013 |
E928536
|
entity |
| Predicate | nextStanleyCupFinal |
P181853
|
FINISHED |
| Object | Stanley Cup 2014 |
—
|
NE NERFINISHED |
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: Stanley Cup 2014 | Statement: [Stanley Cup 2013, nextStanleyCupFinal, Stanley Cup 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nextStanleyCupFinal Context triple: [Stanley Cup 2013, nextStanleyCupFinal, Stanley Cup 2014]
-
A.
nextStanleyCupFinals
chosen
Indicates that one event or time point directly follows the current one as the subsequent Stanley Cup Finals series.
-
B.
StanleyCupFinalSeason
Indicates that the referenced season is the one in which the Stanley Cup Final took place.
-
C.
lastStanleyCupWin
Indicates the event in which a team most recently won the Stanley Cup championship.
-
D.
lostStanleyCupFinals
Indicates that a team was defeated in the championship series of the Stanley Cup Finals.
-
E.
StanleyCupFinalClinchingGameCity
Indicates the city where the Stanley Cup Final’s championship-clinching game took place.
- 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_69f76eb9e66881908534cf22d04c3b5a |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb9e1845e881908d19158440cf3b87 |
completed | May 6, 2026, 8:01 p.m. |
| PD | Predicate disambiguation | batch_69fb8d08d6988190a00794ac26078348 |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:16 p.m.