Triple
T4844643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stalinist architecture |
E108259
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet architecture |
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: Soviet architecture Context triple: [Stalinist architecture, instanceOf, Soviet architecture]
-
A.
socialist realist urban complex
A socialist realist urban complex is a planned architectural and spatial ensemble that embodies socialist ideology through monumental, functional buildings, broad avenues, and integrated public spaces designed to promote collective life and state power.
-
B.
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.
-
C.
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.
-
D.
Soviet design bureau
A Soviet design bureau was a state-controlled, specialized engineering and research organization responsible for conceiving, developing, and prototyping advanced military and industrial technologies within the centrally planned Soviet system.
-
E.
Nordic architecture movement
The Nordic architecture movement is a design approach originating from Northern Europe that emphasizes simplicity, functionality, natural materials, and strong connections to landscape and light.
- 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_69bd4409b264819085ab855f3eb5381a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:25 p.m.