Triple
T32262821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994–95 Central Hockey League |
E824204
|
entity |
| Predicate | pointsForOvertimeWin |
P134355
|
FINISHED |
| Object | 2 |
—
|
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: 2 | Statement: [1994–95 Central Hockey League, pointsForOvertimeWin, 2]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pointsForOvertimeWin Context triple: [1994–95 Central Hockey League, pointsForOvertimeWin, 2]
-
A.
pointsForOvertimeOrShootoutWin
chosen
Indicates that a team is awarded points specifically for winning a game in overtime or a shootout.
-
B.
pointsForOvertimeOrShootoutLoss
Indicates the number of points awarded to a team specifically for losing a game in overtime or a shootout.
-
C.
hasOvertimeWinningMargin
Indicates that one competitor’s margin of victory over another was achieved specifically during an overtime period.
-
D.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
E.
regularSeasonOvertimeLosses
Indicates the number of games a team lost in overtime during the regular 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_69f3490db0748190bfef6e50c95d39d3 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6bc58867c8190bdd3c79f5c9d152f |
completed | May 3, 2026, 3:09 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
Created at: May 1, 2026, 12:41 a.m.