Triple
T19844825
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest Division |
E476831
|
entity |
| Predicate | createdByRealignment |
P72851
|
FINISHED |
| Object | 1998 NHL realignment |
—
|
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: 1998 NHL realignment | Statement: [Northwest Division, createdByRealignment, 1998 NHL realignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: createdByRealignment Context triple: [Northwest Division, createdByRealignment, 1998 NHL realignment]
-
A.
realignedFrom
Indicates that something has been adjusted or repositioned from a previous alignment, configuration, or orientation to a new one.
-
B.
realignedOn
Indicates that something has been adjusted or repositioned so that it is now aligned with a specified reference or standard.
-
C.
createdBy
Indicates that something was brought into existence, produced, or authored through the actions or efforts of a specific agent or entity.
-
D.
formedByRenaming
Indicates that one entity is created or derived from another entity specifically through a change of name.
-
E.
reorganizedDueTo
chosen
Indicates that one entity was reorganized as a consequence of, or in response to, another specified factor, event, or condition.
- 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_69d8e51d39d081909bcfafeaaf3d2fcc |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e658085a148190a305bde0897dfe84 |
completed | April 20, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69e537e21d2881909b1be82f02b99d40 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:51 p.m.