Triple
T27024916
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 NCAA Division I men's ice hockey national championship |
E680758
|
entity |
| Predicate | finalDecidedIn |
P29537
|
FINISHED |
| Object | 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: overtime | Statement: [1991 NCAA Division I men's ice hockey national championship, finalDecidedIn, overtime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalDecidedIn Context triple: [1991 NCAA Division I men's ice hockey national championship, finalDecidedIn, overtime]
-
A.
decidedIn
chosen
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative context.
-
B.
decidedWith
Indicates that an entity made a decision jointly or in agreement with another entity.
-
C.
decisionIsFinal
Indicates that a decision has been conclusively made and cannot be changed, reversed, or appealed.
-
D.
wasDecidedBy
Indicates that a decision or outcome was determined or resolved by a specific agent or authority.
-
E.
hasFinalDecisionOn
Indicates that one entity holds the ultimate authority or responsibility to make and enforce a conclusive decision regarding another entity or matter.
- 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_69eeeb5450988190bfc9a3c012ac463a |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 27, 2026, 7:10 a.m.