Triple
T8732229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cesca Chair |
E207284
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bauhaus design object |
C13454
|
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: Bauhaus design object Context triple: [Cesca Chair, instanceOf, Bauhaus design object]
-
A.
industrial design object
chosen
An industrial design object is a mass-produced, functional product whose form, materials, and user interaction are intentionally shaped to optimize usability, aesthetics, and manufacturability.
-
B.
Streamline Moderne building
A Streamline Moderne building is a late Art Deco architectural form characterized by smooth, curving surfaces, horizontal lines, nautical or aerodynamic motifs, and minimal ornamentation that evoke speed and modernity.
-
C.
readymade sculpture
A readymade sculpture is an artwork created by selecting and presenting an ordinary, often mass-produced object as a sculpture, typically with minimal alteration, to challenge traditional notions of art and authorship.
-
D.
industrial design relationship
An industrial design relationship is the collaborative and often contractual connection between designers, manufacturers, and stakeholders that shapes how functional, aesthetic, and user-centered product solutions are conceived, developed, and brought to market.
-
E.
design bureau
A design bureau is an organization or department that specializes in planning, developing, and refining product, graphic, or architectural designs, often providing creative and technical solutions for clients or internal projects.
- 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_69ca8358e4008190898471a59b96c301 |
completed | March 30, 2026, 2:06 p.m. |
Created at: March 30, 2026, 6:37 p.m.