Triple
T36370336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BKM |
E895735
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural policy authority |
C52425
|
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 authority Context triple: [BKM, instanceOf, cultural policy authority]
-
A.
cultural policy council
A cultural policy council is a formal advisory or decision-making body that develops, guides, and evaluates strategies, regulations, and funding priorities for a community’s cultural life and creative sectors.
-
B.
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.
-
C.
cultural policymaker
chosen
A cultural policymaker is an individual or entity responsible for designing, implementing, and evaluating strategies, regulations, and funding priorities that shape a society’s cultural life, institutions, and creative sectors.
-
D.
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.
-
E.
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.
- 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_69f76e5115588190ad8738860b7bc68b |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.