Triple
T11670413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | English landscape garden style |
E277361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | cultural movement in garden design |
C16776
|
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: cultural movement in garden design Context triple: [English landscape garden style, instanceOf, cultural movement in garden design]
-
A.
landscape design movement
chosen
A landscape design movement is a conceptual class representing a historically or culturally distinct trend in landscape architecture characterized by shared design principles, aesthetics, and approaches to shaping outdoor environments.
-
B.
cultural movement
A cultural movement is a collective, often time-bound shift in values, aesthetics, practices, and ideas within a society or group that seeks to redefine or challenge existing cultural norms.
-
C.
garden design project
A garden design project is a planned endeavor that organizes and coordinates the creation or transformation of an outdoor space to achieve specific aesthetic, functional, and environmental goals.
-
D.
landscape design series
A landscape design series is a cohesive collection of related outdoor space plans or projects that explore and apply recurring design principles, themes, and elements across multiple sites or contexts.
-
E.
landscape art movement
A landscape art movement is a collective trend or period in art history characterized by artists’ shared focus on depicting natural scenery and environments, often reflecting specific aesthetic, cultural, or philosophical ideals.
- 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_69d6aafd0a448190b44da30af8c6c519 |
completed | April 8, 2026, 7:22 p.m. |
Created at: April 8, 2026, 9:39 p.m.