Triple
T32913750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UC Berkeley performing arts facilities |
E841949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | performing arts venue network |
C42014
|
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: performing arts venue network Context triple: [UC Berkeley performing arts facilities, instanceOf, performing arts venue network]
-
A.
performing arts venue group
chosen
A performing arts venue group is an organization that owns, manages, or coordinates multiple performance spaces—such as theaters, concert halls, and auditoriums—to present and support live artistic productions.
-
B.
network of concert venues
A network of concert venues is an interconnected system of performance spaces that coordinate scheduling, promotion, and resources to host live music and entertainment events across multiple locations.
-
C.
arts venue
An arts venue is a dedicated space where artistic performances, exhibitions, or cultural events are presented to the public.
-
D.
performing and visual arts center
A performing and visual arts center is a dedicated facility that hosts, presents, and supports a variety of live performances and visual art exhibitions, often including theaters, galleries, studios, and related educational spaces.
-
E.
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.
- 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_69f3494779388190a5d3e97f92278be2 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:19 a.m.