Triple
T8027559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2020–21 NHL season |
E186892
|
entity |
| Predicate | hadRealignedDivisions |
P3196
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [2020–21 NHL season, hadRealignedDivisions, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadRealignedDivisions Context triple: [2020–21 NHL season, hadRealignedDivisions, true]
-
A.
divisionRealignment
chosen
Indicates a reorganization of how entities are grouped into divisions, typically involving changes to which entities belong to which division.
-
B.
divisionalAlignment
Indicates that one entity is organized, positioned, or associated in accordance with the structure, boundaries, or strategy of a particular division within a larger organization.
-
C.
hadInternalDivision
Indicates that an entity experienced a split or conflict within its own members, factions, or components.
-
D.
capitalDivision
Indicates that one administrative division serves as the capital of another administrative division or political entity.
-
E.
realignedFrom
Indicates that something has been adjusted or repositioned from a previous alignment, configuration, or orientation to a new one.
- 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_69ca82ad4e2c8190a693e3c9e30fe66f |
completed | March 30, 2026, 2:03 p.m. |
| NER | Named-entity recognition | batch_69cb3eccacb0819082f7c3d6fd48e3c4 |
completed | March 31, 2026, 3:26 a.m. |
| PD | Predicate disambiguation | batch_69cb049253d08190bafcecfde493ab8b |
completed | March 30, 2026, 11:17 p.m. |
Created at: March 30, 2026, 5:21 p.m.