Triple
T14538005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1935–36 NHL season |
E341098
|
entity |
| Predicate | StanleyCupFinalsFormat |
P92809
|
FINISHED |
| Object | best-of-five series |
—
|
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: best-of-five series | Statement: [1935–36 NHL season, StanleyCupFinalsFormat, best-of-five series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: StanleyCupFinalsFormat Context triple: [1935–36 NHL season, StanleyCupFinalsFormat, best-of-five series]
-
A.
StanleyCupFormat
Indicates the specific structure, rules, and progression format used to organize and play the Stanley Cup competition.
-
B.
finalsSeriesFormat
chosen
Indicates the specific structure or rules governing how a finals series is organized and played (e.g., number of games, sequence, and format).
-
C.
StanleyCupFinalsSeriesResult
Indicates the outcome of a Stanley Cup Finals series, specifying which team won and by what series score.
-
D.
WorldSeriesFormat
Indicates the specific competitive structure or rules used to organize and play a World Series matchup.
-
E.
StanleyCupFinalsGames
Indicates a relationship where specific games are identified as belonging to the Stanley Cup Finals series in a given season.
- 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_69d822dac79c8190a84a073f3cbaced5 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb1bb90008190947ac0961393446d |
completed | April 14, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69de5c546c7081909e27d504ec360c5c |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:22 a.m.