Triple
T10233125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decree of the Presidium of the Supreme Soviet of the USSR of 10 October 1943 |
E243393
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet decree |
C3512
|
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 decree Context triple: [Decree of the Presidium of the Supreme Soviet of the USSR of 10 October 1943, instanceOf, Soviet decree]
-
A.
Communist Party of Russia resolution
A Communist Party of Russia resolution is a formal, collectively adopted document that outlines the party’s official position, decisions, or directives on specific political, ideological, or organizational issues within the Russian context.
-
B.
decree
chosen
A decree is an authoritative and formal order or decision issued by a person or body with legal or official power, often carrying the force of law.
-
C.
Soviet document
A Soviet document is an official or unofficial written record produced within the Soviet Union’s political, administrative, or social systems, reflecting its bureaucratic procedures, ideology, and historical context.
-
D.
Soviet government position
A Soviet government position is an official role within the political and administrative hierarchy of the USSR, responsible for implementing Communist Party policies and managing state functions at various levels.
-
E.
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.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:20 a.m.