Triple
T26777728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2009 NCAA Division I men's ice hockey championship |
E670162
|
entity |
| Predicate | finalNickname |
P178011
|
FINISHED |
| Object | Frozen Four championship game |
—
|
NE NERFINISHED |
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: Frozen Four championship game | Statement: [2009 NCAA Division I men's ice hockey championship, finalNickname, Frozen Four championship game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalNickname Context triple: [2009 NCAA Division I men's ice hockey championship, finalNickname, Frozen Four championship game]
-
A.
nameFinal
Indicates that this is the final or definitive name assigned to an entity, as opposed to a temporary, intermediate, or previous name.
-
B.
changedNicknameTo
Indicates that an entity has altered another entity’s nickname to a specified new nickname.
-
C.
localNickname
Indicates that an entity is known by a particular nickname within a specific local or regional context.
-
D.
nickNameGivenBy
Indicates that one entity assigns or uses a particular nickname for another entity.
-
E.
stageNickname
Indicates that one entity is the stage name or performance nickname used by another entity.
- 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f707f7959881908f037f0d6b1d0c36 |
completed | May 3, 2026, 8:31 a.m. |
| PD | Predicate disambiguation | batch_69f700fc274c8190a128593dc7c7abd0 |
completed | May 3, 2026, 8:02 a.m. |
| PDg | Predicate description generation | batch_69f707f380388190954b79d52a321921 |
completed | May 3, 2026, 8:31 a.m. |
Created at: April 27, 2026, 4:06 a.m.