Triple
T134288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SU |
E2716
|
entity |
| Predicate | changeReason |
P5019
|
FINISHED |
| Object | dissolution of the Soviet Union |
—
|
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: dissolution of the Soviet Union | Statement: [SU, changeReason, dissolution of the Soviet Union]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changeReason Context triple: [SU, changeReason, dissolution of the Soviet Union]
-
A.
causeOfChangeOfDestination
Indicates that one entity is the reason or trigger for another entity changing its intended destination.
-
B.
nameChangeReason
Indicates the reason or justification for a change in an entity’s name.
-
C.
selectionReason
Indicates the reason or justification for choosing or selecting one entity over alternatives.
-
D.
reasonForRelocation
Indicates the underlying cause, motivation, or circumstance that led an entity to move from one location to another.
-
E.
reasonForMerger
Indicates the underlying cause, motivation, or justification for why two or more entities merged.
- F. None of above. chosen
Provenance (4 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a25788b2688190a45b39447f702551 |
completed | Feb. 28, 2026, 2:48 a.m. |
| PD | Predicate disambiguation | batch_69a25650251c81908a6ea6368cd61198 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a256ea776081908fec36c3fdfb8d84 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.