Triple
T10108031
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Glavlit |
E218173
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet state censorship agency |
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 censorship agency Context triple: [Glavlit, instanceOf, Soviet state censorship agency]
-
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.
government agency of Russia
A government agency of Russia is an official state body established by the Russian Federation to implement public policy, administer specific functions, and provide services within a defined area of governance under federal or regional authority.
-
C.
Russian federal agency
A Russian federal agency is a government body established by the Russian Federation to implement federal laws, execute state policies, and manage specific administrative functions across the country.
-
D.
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.
-
E.
period of the Soviet security services
The period of the Soviet security services encompasses the historical evolution, organizational structures, operational practices, and political roles of Soviet state security organs from the Bolshevik Revolution through the dissolution of the USSR.
- 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_69ca83da93fc8190b54e44bc2b34857c |
completed | March 30, 2026, 2:08 p.m. |
Created at: March 30, 2026, 9:03 p.m.