Triple
T6608141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greater Manchester media cluster |
E149169
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | creative industries cluster |
C2351
|
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: creative industries cluster Context triple: [Greater Manchester media cluster, instanceOf, creative industries cluster]
-
A.
cultural industry
chosen
A cultural industry is an economic sector that produces, distributes, and commercializes cultural goods and services—such as film, music, publishing, and the arts—shaping social values and identities while generating financial value.
-
B.
creative park
A creative park is a public or semi-public space intentionally designed to inspire imagination and innovation through interactive art, flexible work areas, and playful, collaborative environments.
-
C.
performing arts ecosystem
A performing arts ecosystem is an interconnected network of artists, organizations, venues, audiences, funding bodies, and support services that collectively create, present, sustain, and evolve live artistic performances within a cultural and economic context.
-
D.
business community
A business community is a network of individuals and organizations that interact, collaborate, and share resources within a commercial or professional context to achieve mutual economic and strategic goals.
-
E.
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.
- 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_69c687eaa7508190bb58ce2aa02039b3 |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 1:57 p.m.