Triple
T29864630
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario Junior Hockey League |
E758417
|
entity |
| Predicate | hasOvertimeFormat |
P3767
|
FINISHED |
| Object | regular season overtime and shootout rules |
—
|
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: regular season overtime and shootout rules | Statement: [Ontario Junior Hockey League, hasOvertimeFormat, regular season overtime and shootout rules]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOvertimeFormat Context triple: [Ontario Junior Hockey League, hasOvertimeFormat, regular season overtime and shootout rules]
-
A.
usesOvertime
Indicates that one entity makes use of another entity repeatedly or continuously over an extended period of time.
-
B.
allowsOvertime
Indicates that one entity permits another entity to work beyond standard or scheduled time limits.
-
C.
overtimeFormatRegularSeason
chosen
Indicates the format or rules used for overtime periods specifically during the regular season.
-
D.
overtimePeriodDuration
Indicates the length of time that an overtime period lasts.
-
E.
overtimeRule
Indicates the rule or policy that defines when and how overtime work is calculated or applied.
- 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_69f2245b4dec8190b85f664d918a00a5 |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f67688760481908e28d887d583e8c4 |
completed | May 2, 2026, 10:11 p.m. |
| PD | Predicate disambiguation | batch_69f66ac32b60819092290b2de35988d3 |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 29, 2026, 5:51 p.m.