Triple
T19301876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHL Adams Division |
E482719
|
entity |
| Predicate | realignmentContext |
P46340
|
FINISHED |
| Object | Created during 1974 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: Created during 1974 NHL realignment | Statement: [NHL Adams Division, realignmentContext, Created during 1974 NHL realignment]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: realignmentContext Context triple: [NHL Adams Division, realignmentContext, Created during 1974 NHL realignment]
-
A.
relocationContext
Indicates the circumstances, reasons, and situational details surrounding an entity’s move or transfer from one place or position to another.
-
B.
realignedFrom
chosen
Indicates that something has been adjusted or repositioned from a previous alignment, configuration, or orientation to a new one.
-
C.
realignedOn
Indicates that something has been adjusted or repositioned so that it is now aligned with a specified reference or standard.
-
D.
contextOfRenaming
Indicates the situational or historical context in which an entity’s name was or is being changed.
-
E.
alignmentChange
Indicates a change in the moral, ethical, or factional stance of an entity relative to its previous alignment.
- 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_69d8e8d04d5c8190baa816986f2b1d1e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fc8a2a5c8190bfe95e40d3c93a42 |
completed | April 20, 2026, 10:14 a.m. |
| PD | Predicate disambiguation | batch_69e4dd0bc7508190a6f9d56bd4c3404f |
completed | April 19, 2026, 1:47 p.m. |
Created at: April 10, 2026, 1:31 p.m.