Triple
T10918318
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BFI Film Fund |
E257882
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural funding programme |
C9830
|
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 funding programme Context triple: [BFI Film Fund, instanceOf, cultural funding programme]
-
A.
cultural heritage programme
A cultural heritage programme is an organized set of initiatives designed to identify, preserve, promote, and transmit a community’s tangible and intangible cultural assets across generations.
-
B.
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.
-
C.
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.
-
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
chosen
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_69d6aa864ed88190818280ab6791d065 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:22 p.m.