Triple
T28079794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | USSR Council of Ministers decrees of 1965–1966 |
E709644
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet legal act |
C13140
|
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 legal act Context triple: [USSR Council of Ministers decrees of 1965–1966, instanceOf, Soviet legal act]
-
A.
Czechoslovak legal decree
A Czechoslovak legal decree is a formal, state-issued legal act or regulation that had the force of law in Czechoslovakia, typically used to implement, interpret, or modify existing legislation or policy.
-
B.
Soviet document
chosen
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.
-
C.
Russian federal law
A Russian federal law is a legally binding normative act adopted by the Federal Assembly and signed by the President of Russia, regulating key areas of public and private life across the entire Russian Federation.
-
D.
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.
-
E.
Ukrainian legislation
Ukrainian legislation is the system of legal norms, acts, and regulations adopted by competent Ukrainian authorities that govern social relations, define rights and obligations, and establish the legal framework of the state.
- 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_69ef9b7037f0819095bb90eaccbcaf32 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 8:51 p.m.