Triple
T25494962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Follies |
E638934
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | architectural installation series |
C24968
|
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: architectural installation series Context triple: [Red Follies, instanceOf, architectural installation series]
-
A.
art installation series
An art installation series is a cohesive collection of site-specific or spatially arranged artworks presented sequentially or in relation to one another to explore a unifying concept, narrative, or sensory experience.
-
B.
public art installation series
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.
-
C.
architectural work series
chosen
An architectural work series is a curated collection of related architectural projects or designs that share a common theme, style, purpose, or conceptual framework and are presented together as a cohesive body of work.
-
D.
exhibition design series
A curated sequence of exhibitions unified by a cohesive design language, exploring how spatial, visual, and experiential elements evolve across multiple show environments.
-
E.
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.
- 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_69e75dbbd2a88190b70e1e645de14b9a |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 2:40 p.m.