Triple
T18813748
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northern Arts |
E460081
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional arts funding body |
C9954
|
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: regional arts funding body Context triple: [Northern Arts, instanceOf, regional arts funding body]
-
A.
arts funding agency
chosen
An arts funding agency is an organization that allocates financial and other resources to support artists, cultural institutions, and creative projects in order to foster artistic development and public access to the arts.
-
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.
public funding body
A public funding body is a government or publicly mandated organization that allocates financial resources to support projects, institutions, or activities in line with public policy goals and societal needs.
-
D.
patron of the arts
A patron of the arts is an individual or organization that supports artists and artistic endeavors, typically through financial backing, resources, or advocacy, to foster the creation and preservation of art.
-
E.
performing arts center management organization
A performing arts center management organization oversees the strategic planning, operations, programming, and financial sustainability of a performance venue or complex, coordinating artistic, technical, and administrative functions to serve artists and audiences.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.