Triple
T24292867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | rural cemetery movement |
E605871
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | landscape architecture movement |
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: landscape architecture movement Context triple: [rural cemetery movement, instanceOf, landscape architecture movement]
-
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.
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.
-
C.
landscape architecture treatise
A landscape architecture treatise is a comprehensive, theoretically grounded written work that systematically explores principles, methods, and philosophies for designing and managing outdoor spaces and environments.
-
D.
landscape architecture department
A landscape architecture department is an academic unit that educates students and conducts research on the planning, design, and management of outdoor spaces and environments.
-
E.
landscape architecture plan
A landscape architecture plan is a detailed, scaled drawing that illustrates the design, layout, and intended use of outdoor spaces, including plantings, hardscapes, circulation, and site features.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.