Triple
T319366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL playoffs |
E7777
|
entity |
| Predicate | overtimeFormat |
P3769
|
FINISHED |
| Object | 5-on-5 skaters plus goalies |
—
|
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: 5-on-5 skaters plus goalies | Statement: [NHL playoffs, overtimeFormat, 5-on-5 skaters plus goalies]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overtimeFormat Context triple: [NHL playoffs, overtimeFormat, 5-on-5 skaters plus goalies]
-
A.
overtimeFormatRegularSeason
Indicates the format or rules used for overtime periods specifically during the regular season.
-
B.
overtimeFormatPlayoffs
chosen
Indicates that the relationship or action pertains to the specific overtime rules or structure used during playoff games, as distinct from regular-season overtime formats.
-
C.
overtimeRule
Indicates the rule or policy that defines when and how overtime work is calculated or applied.
-
D.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
E.
timeNotation
Indicates the specific system or format used to represent and write times (e.g., 12-hour vs 24-hour notation).
- 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_69a2e7e7af7881908890039d6be4e9b8 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2eb7df63c8190b7cd1bcfdfd96187 |
completed | Feb. 28, 2026, 1:19 p.m. |
| PD | Predicate disambiguation | batch_69a2e94513ec819089f5177f7a521e65 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.