Triple
T8040673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zhdanovshchina cultural campaign |
E187427
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural policy campaign |
C533
|
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: cultural policy campaign Context triple: [Zhdanovshchina cultural campaign, instanceOf, cultural policy campaign]
-
A.
cultural policy
Cultural policy is the set of principles, decisions, and actions through which governments and institutions shape the production, distribution, access to, and preservation of cultural expressions and heritage.
-
B.
cultural policy instrument
A cultural policy instrument is a deliberate tool, mechanism, or measure used by public authorities or institutions to influence, support, regulate, or shape cultural activities, expressions, and sectors in line with specific policy goals.
-
C.
cultural policy instrument
A cultural policy instrument is a deliberate tool or mechanism—such as funding schemes, regulations, incentives, or programs—used by public authorities to shape, support, or influence cultural production, distribution, and participation.
-
D.
cultural movement
chosen
A cultural movement is a collective, often time-bound shift in values, aesthetics, practices, and ideas within a society or group that seeks to redefine or challenge existing cultural norms.
-
E.
landmark cultural policy law
A landmark cultural policy law is a transformative legal framework that fundamentally reshapes how a society protects, funds, and promotes its cultural heritage, creative industries, and artistic expression.
- 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_69ca82b00cb48190b59a300f70e97bd7 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:23 p.m.