Triple
T33881927
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 NCAA Division I men’s ice hockey championship |
E868514
|
entity |
| Predicate | numberOfOvertimes |
P47869
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [1984 NCAA Division I men’s ice hockey championship, numberOfOvertimes, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfOvertimes Context triple: [1984 NCAA Division I men’s ice hockey championship, numberOfOvertimes, 4]
-
A.
overtimePlayed
Indicates that an activity, event, or game continued beyond its regular or scheduled duration into an additional overtime period.
-
B.
overtimePeriodCount
chosen
Indicates the number of overtime periods that occurred or are allocated in a given event or context.
-
C.
longestGameOvertimes
Indicates the number of overtime periods played in the longest game (by duration or overtime count) within a given context.
-
D.
game7Overtimes
Indicates that a game extended into a seventh overtime period, reflecting an exceptionally prolonged and closely contested match.
-
E.
overtimePeriodDuration
Indicates the length of time that an overtime period lasts.
- 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_69f34995b81c8190acdb45cea5a10eff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_6a035b78140081908e451cb63d3c1c7c |
completed | May 12, 2026, 4:55 p.m. |
| PD | Predicate disambiguation | batch_6a035af3d8f48190bf1f3741d374404e |
completed | May 12, 2026, 4:53 p.m. |
Created at: May 1, 2026, 1:48 a.m.