Triple
T27024933
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1991 NCAA Division I men's ice hockey national championship |
E680758
|
entity |
| Predicate | championTitleCountForProgram |
P155255
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [1991 NCAA Division I men's ice hockey national championship, championTitleCountForProgram, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championTitleCountForProgram Context triple: [1991 NCAA Division I men's ice hockey national championship, championTitleCountForProgram, 1]
-
A.
numberOfChampionTitles
chosen
Indicates the total count of championship titles that an entity has won.
-
B.
championTitleCountFranchise
Indicates the number of championship titles a franchise has won.
-
C.
consecutiveTitleNumberForChampion
Indicates that the associated number represents how many titles a champion has won consecutively up to that point.
-
D.
championsTitleWonBy
Indicates that a particular championship title is held or has been won by a specific entity.
-
E.
consecutiveTitlesForChampion
Indicates that a champion has won multiple titles in succession without interruption.
- 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_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 27, 2026, 7:10 a.m.