Triple
T23657613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | green building movement |
E584349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sustainable design movement |
C17239
|
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: sustainable design movement Context triple: [green building movement, instanceOf, sustainable design movement]
-
A.
sustainable design project
A sustainable design project is an initiative that plans, develops, and implements solutions minimizing environmental impact while balancing social responsibility and economic viability throughout a product, service, or system’s life cycle.
-
B.
sustainable design feature
A sustainable design feature is an element intentionally integrated into a product, building, or system to reduce environmental impact, conserve resources, and support long-term ecological and human well-being.
-
C.
sustainability initiative
A sustainability initiative is a coordinated set of actions, policies, and programs designed to reduce environmental impact, conserve resources, and promote long-term ecological, social, and economic well-being.
-
D.
environmental movement
chosen
The environmental movement is a collective social and political effort aimed at protecting natural ecosystems, conserving resources, and promoting sustainable practices to address environmental degradation and climate change.
-
E.
urban design movement
An urban design movement is a collective, often time-bound approach to shaping cities’ physical form, public spaces, and infrastructure based on shared social, cultural, environmental, and aesthetic principles.
- 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_69e248ffc0888190ae23c4731eb8b7ac |
completed | April 17, 2026, 2:51 p.m. |
Created at: April 17, 2026, 6:49 p.m.