Triple
T3708028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Azerbaijan SSR administrative divisions |
E80939
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet administrative structure |
C14146
|
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 administrative structure Context triple: [Azerbaijan SSR administrative divisions, instanceOf, Soviet administrative structure]
-
A.
Soviet government ministry
A Soviet government ministry was a centralized state administrative body responsible for directing and managing a specific sector of the economy, society, or state functions under the authority of the USSR’s Communist Party leadership.
-
B.
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.
-
C.
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.
-
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 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.
- F. None of above. chosen
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_69ad8b1793888190a5f70e4b21dc05a1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:33 p.m.