Triple
T18787090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Riverhouse |
E459404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | eco-friendly building |
C20840
|
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: eco-friendly building Context triple: [Riverhouse, instanceOf, eco-friendly building]
-
A.
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.
-
B.
building envelope
The building envelope is the physical barrier between the interior and exterior of a building, including walls, roofs, windows, doors, and foundations, that controls the flow of heat, air, moisture, and light.
-
C.
sustainable design project
chosen
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.
-
D.
green building certification system
A green building certification system is a standardized framework that evaluates and rates buildings based on their environmental performance, resource efficiency, and sustainability practices throughout design, construction, and operation.
-
E.
eco-friendly shop
An eco-friendly shop is a retail store that prioritizes environmentally sustainable products and practices, such as selling low-impact goods, minimizing waste, and using renewable or recycled materials.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:52 a.m.