Triple
T6258270
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ural Soviet |
E140228
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional Soviet authority |
C8127
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: regional Soviet authority Context triple: [Ural Soviet, instanceOf, regional Soviet authority]
-
A.
Soviet administrative structure
The Soviet administrative structure was a highly centralized, hierarchical system of governance in which the Communist Party controlled state institutions, economic planning, and regional authorities through overlapping layers of bureaucratic and political oversight.
-
B.
regional legislature of Russia
A regional legislature of Russia is a representative elected body at the subnational (federal subject) level that enacts laws, approves budgets, and oversees executive authorities within its respective region in accordance with the Russian Federation’s constitutional framework.
-
C.
autonomous okrug of Russia
An autonomous okrug of Russia is a type of federal subject with a degree of self-governance, typically established in areas with significant indigenous or ethnic minority populations and often administratively associated with a larger region or krai.
-
D.
policy of the Soviet Union
The policy of the Soviet Union encompasses the ideological, political, economic, and foreign strategies implemented by the Soviet state to build and maintain a socialist system under one-party rule from 1917 to 1991.
-
E.
soviet
chosen
Soviet refers to anything related to the former Soviet Union (USSR), including its government, ideology, culture, or people associated with its socialist, one-party state system.
- F. None of above.
Provenance (1 batch)
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_69c008c95c5c819084bd3dd56133d84d |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:24 p.m.