Triple
T11370081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NCAA Division I ice hockey |
E269317
|
entity |
| Predicate | championshipParticipants |
P29812
|
FINISHED |
| Object | 16 teams |
—
|
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: 16 teams | Statement: [NCAA Division I ice hockey, championshipParticipants, 16 teams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championshipParticipants Context triple: [NCAA Division I ice hockey, championshipParticipants, 16 teams]
-
A.
championshipFor
Indicates that a championship event or title is held, awarded, or designated for a particular competition, season, or category.
-
B.
finalTournamentParticipants
chosen
Indicates that the specified entities are the participants who qualified for and compete in the final round of a tournament.
-
C.
championshipStart
Indicates the date or point in time when a championship event or competition begins.
-
D.
championshipSeries
Indicates a competitive series of contests or games that determines a champion between qualifying participants.
-
E.
championshipName
Indicates the name or title assigned to a specific championship event or competition.
- 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_69d6aacca1048190b39dbbc2174616fa |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d800160a1c81909d115bf89fe54a49 |
completed | April 9, 2026, 7:37 p.m. |
| PD | Predicate disambiguation | batch_69d7e7022d508190996f9be0847c2b41 |
completed | April 9, 2026, 5:50 p.m. |
Created at: April 8, 2026, 9:33 p.m.