Triple
T14467851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Division (NHL) |
E358759
|
entity |
| Predicate | championDesignation |
P2682
|
FINISHED |
| Object | Central Division champion |
—
|
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: Central Division champion | Statement: [Central Division (NHL), championDesignation, Central Division champion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: championDesignation Context triple: [Central Division (NHL), championDesignation, Central Division champion]
-
A.
championOf
Indicates that one entity serves as the primary defender, advocate, or leading supporter of another entity, often working to promote or protect its interests.
-
B.
champion
chosen
Indicates that one entity has won a competition or contest and holds the top position or title over others.
-
C.
championedBy
Indicates that an entity is actively supported, promoted, or advocated for by another entity.
-
D.
championNationality
Indicates the country or nationality that a champion represents or is associated with.
-
E.
championManager
Indicates that one entity serves as the manager, coach, or primary overseer responsible for the success or performance of a champion entity.
- 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_69d827966698819082e140837737501d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de91f8613c819080424104c0b7f4c3 |
completed | April 14, 2026, 7:14 p.m. |
| PD | Predicate disambiguation | batch_69de5c42bd3c81909a62acf30cc24d1e |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.