Triple
T27984175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1946 Central Committee resolution on the journals Zvezda and Leningrad |
E706701
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | censorship measure |
C53625
|
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: censorship measure Context triple: [1946 Central Committee resolution on the journals Zvezda and Leningrad, instanceOf, censorship measure]
-
A.
censorship law
Censorship law is the body of legal rules and regulations that restrict, control, or prohibit the creation, distribution, or access to certain forms of expression, media, or information.
-
B.
censorship index
A censorship index is a quantitative measure that rates the extent and severity of information control, content restriction, and suppression of expression within a given medium, institution, or jurisdiction.
-
C.
censorship-circumvention system
A censorship-circumvention system is a technical framework that enables users to access, share, and receive information freely by bypassing or obfuscating network-level, platform-level, or state-imposed content restrictions.
-
D.
defensive measure
A defensive measure is an action, system, or strategy designed to protect against, reduce, or mitigate harm from potential threats or attacks.
-
E.
denazification measure
A denazification measure is an action or policy implemented to identify, remove, and prevent the influence of Nazi ideology, symbols, organizations, or individuals from public, political, cultural, or institutional life.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:46 p.m.