Triple
T32271175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 NCAA Division I Men's Ice Hockey Championship |
E824416
|
entity |
| Predicate | frozenFourStartDate |
P174877
|
FINISHED |
| Object | 2013-04-11 |
—
|
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: 2013-04-11 | Statement: [2013 NCAA Division I Men's Ice Hockey Championship, frozenFourStartDate, 2013-04-11]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: frozenFourStartDate Context triple: [2013 NCAA Division I Men's Ice Hockey Championship, frozenFourStartDate, 2013-04-11]
-
A.
frozenFourParticipants
Indicates that the entities are teams that qualified for and participated in the NCAA Division I men’s ice hockey Frozen Four tournament in a given year.
-
B.
frozenFourRunnerUp
Indicates that a team finished as the runner-up (lost in the championship game) in the NCAA men's ice hockey Frozen Four tournament.
-
C.
frozenOn
Indicates that one entity becomes immobile or inactive at a specific time, event, or condition, as if stopped or preserved in its current state.
-
D.
finalFourEndDate
Indicates the date on which the Final Four event or phase concludes.
-
E.
frozenInYear
Indicates that an entity was frozen or preserved in a specific calendar year.
- F. None of above. chosen
Provenance (4 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_69f3490e73588190915f282edd105772 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c90790788190a1ed09adc86ed22d |
completed | May 3, 2026, 4:03 a.m. |
| PD | Predicate disambiguation | batch_69f6c3f42fbc8190a06eb1044c9e6094 |
completed | May 3, 2026, 3:41 a.m. |
| PDg | Predicate description generation | batch_69f6c814c26c81908f5c47285129ff2a |
completed | May 3, 2026, 3:59 a.m. |
Created at: May 1, 2026, 12:42 a.m.