Triple
T5482262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dalstroy |
E123493
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet state organization |
C16774
|
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: Soviet state organization Context triple: [Dalstroy, instanceOf, Soviet state organization]
-
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.
supreme soviet
The Supreme Soviet was the highest legislative body in the Soviet Union (and in its constituent republics), formally empowered to enact laws, approve plans and budgets, and elect key state officials, though in practice it largely ratified decisions made by the Communist Party leadership.
-
C.
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.
-
D.
soviet
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.
-
E.
Soviet organization
chosen
A Soviet organization is an institution, agency, or collective entity established under the governance and ideological framework of the Soviet Union to manage political, economic, social, or military functions.
- 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_69bd4648883481909e9775d43300c5fa |
completed | March 20, 2026, 1:06 p.m. |
Created at: March 20, 2026, 2:09 p.m.