Triple
T18361965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2001 Stanley Cup Playoffs |
E439939
|
entity |
| Predicate | secondRoundFormat |
P130811
|
FINISHED |
| Object | best-of-seven |
—
|
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-seven | Statement: [2001 Stanley Cup Playoffs, secondRoundFormat, best-of-seven]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: secondRoundFormat Context triple: [2001 Stanley Cup Playoffs, secondRoundFormat, best-of-seven]
-
A.
secondRoundDate
Indicates the date on which the second round of an event, process, or sequence is scheduled or occurs.
-
B.
secondRoundEndDate
Indicates the date on which the second round of an event, process, or activity concludes.
-
C.
includesSecondRound
Indicates that the referenced process, event, or activity contains or involves a second round or phase as part of its structure.
-
D.
secondRoundSeriesResult
Indicates the outcome or result of a series that takes place in the second round of a multi-round competition or tournament.
-
E.
secondRoundCandidate
Indicates that an entity has advanced past an initial selection stage and is being considered as a candidate in a second round of evaluation or decision-making.
- 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_69d8b918221c8190a9f7b563d64ac677 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e516dbd4748190a6c5715ef943bd4a |
completed | April 19, 2026, 5:54 p.m. |
| PD | Predicate disambiguation | batch_69e44fed3fdc81908f4ed6a81db42416 |
completed | April 19, 2026, 3:45 a.m. |
| PDg | Predicate description generation | batch_69e451a1bda48190a9cd1db436d4be62 |
completed | April 19, 2026, 3:53 a.m. |
Created at: April 10, 2026, 10:37 a.m.