Triple
T24210960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stuart Collection at UC San Diego |
E600541
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | site-specific art program |
C27894
|
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: site-specific art program Context triple: [Stuart Collection at UC San Diego, instanceOf, site-specific art program]
-
A.
site-specific art installation
A site-specific art installation is a work of art created to exist in a particular place, with its meaning, form, and experience shaped by the physical, social, and historical context of that location.
-
B.
visual arts program
A visual arts program is an organized course of study or series of activities designed to develop skills, knowledge, and creative expression in disciplines such as drawing, painting, sculpture, and digital media.
-
C.
public art installation series
chosen
A public art installation series is a curated sequence of site-specific artworks displayed in shared communal spaces over time, designed to engage diverse audiences and provoke reflection, dialogue, or interaction within the public realm.
-
D.
art exhibition program
An art exhibition program is a curated schedule and accompanying materials that outline the artworks, artists, themes, and events presented within a specific exhibition.
-
E.
cultural institution program
A cultural institution program is a structured set of activities, events, or initiatives designed by a cultural organization to engage audiences, interpret and present cultural content, and fulfill its educational, artistic, or social mission.
- 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_69e2953344c48190875730c7d52112a0 |
completed | April 17, 2026, 8:16 p.m. |
Created at: April 17, 2026, 11:55 p.m.