Triple
T38009490
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Let’s Create |
E948326
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Arts Council England strategy |
C23458
|
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: Arts Council England strategy Context triple: [Let’s Create, instanceOf, Arts Council England strategy]
-
A.
Arts Council England programme
An Arts Council England programme is an initiative or funding scheme designed and administered by Arts Council England to support and develop arts, culture, and creativity across communities in England.
-
B.
cultural policy council
chosen
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.
UK City of Culture
A UK City of Culture is a designated city selected by the UK government to host a year-long program of cultural events and activities aimed at celebrating local arts, boosting tourism, and driving social and economic regeneration.
-
D.
public arts initiative
A public arts initiative is a coordinated program or project that commissions, supports, or presents artistic works in shared community spaces to foster cultural engagement, accessibility, and civic identity.
-
E.
Scottish cultural work
A Scottish cultural work is a creative or intellectual production—such as literature, music, film, art, or performance—that is produced in Scotland or by Scottish creators and meaningfully reflects, represents, or engages with Scottish history, society, or identity.
- 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_69f76efb4b10819092c8c2ba28ac06a8 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.