Triple
T33881948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 NCAA Division I men’s ice hockey championship |
E868514
|
entity |
| Predicate | decisiveGoalPeriod |
P51805
|
FINISHED |
| Object | fourth overtime |
—
|
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: fourth overtime | Statement: [1984 NCAA Division I men’s ice hockey championship, decisiveGoalPeriod, fourth overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decisiveGoalPeriod Context triple: [1984 NCAA Division I men’s ice hockey championship, decisiveGoalPeriod, fourth overtime]
-
A.
decidingGoalPeriod
Indicates that an agent is in the process of choosing or determining a specific time period for a goal or objective.
-
B.
decisiveGoalGame
Indicates that a game contains a goal or scoring event that definitively determines the winner or final outcome.
-
C.
decidingGoalMinute
Indicates the minute in a match when a goal is scored that ultimately decides the outcome (e.g., the winning or decisive goal).
-
D.
clinchingGoalPeriod
chosen
Indicates the time period or segment of play during which the decisive, game-clinching goal was scored.
-
E.
decidingScoreTime
Indicates the point in time at which a decisive or game-determining score occurs.
- 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_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: May 1, 2026, 1:48 a.m.