Triple
T3226523
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vancouver Canucks |
E67635
|
entity |
| Predicate | StanleyCupFinalAppearances |
P2219
|
FINISHED |
| Object | 1982 |
—
|
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: 1982 | Statement: [Vancouver Canucks, StanleyCupFinalAppearances, 1982]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StanleyCupFinalAppearances Context triple: [Vancouver Canucks, StanleyCupFinalAppearances, 1982]
-
A.
stanleyCupFinalsAppearance
chosen
Indicates that an entity (typically a hockey team) has participated in the Stanley Cup Finals in a given season or year.
-
B.
StanleyCupChampionships
Indicates the number of times an entity has won the Stanley Cup championship.
-
C.
StanleyCupWinningSeasons
Indicates the seasons in which a team won the Stanley Cup championship.
-
D.
stanleyCupWinYear
Indicates the specific year in which a given team won the Stanley Cup.
-
E.
StanleyCupWinnerWith
Indicates that one entity is the winner of the Stanley Cup in association with, or while being a member of, the other entity (typically a team or organization).
- 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_69ad858c61888190a31196310d9b30b5 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adaeb4cd3481908af8a2c9b6c0742d |
completed | March 8, 2026, 5:15 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.