52/100

Moderate evidence

ProblemPublished recordClimateProblem Space

Towards trustworthy LLM-assisted EPD comparability assessment for circular construction materials

Truvace record
TRV-2026-2700raw data (JSON)
Version
v1Published
First published
Evidence type
Benchmark or lab evaluation
Sources
1 sourcePeer-reviewed
sha256
c416c14efba3…check it

Environmental Product Declarations (EPDs) are increasingly used to support construction material selection, but their comparability depends on how system boundaries and allocation rules are interpreted. Although large language models (LLMs) are increasingly explored for sustainability assessment, limited attention has been given to how methodological ambiguity affects LLM reasoning reliability and comparability judgement. This study investigates how LLMs interpret A1–A3 carbon emissions in EPDs for virgin and re…

The problem

A study testing GPT-5.3, Qwen 3.6-Plus and Gemini 3 on carbon declarations for virgin and recycled aggregates found zero-shot models often defaulted to calling products non-comparable, and rule-based prompts that raised accuracy also made answers less stable.

What this doesn’t fix

The evaluation covered only two case materials, virgin aggregates and recycled concrete aggregates, and A1–A3 emissions, so results may not extend to other materials or life-cycle stages.

Sources

1 on file
  1. Environmental Impact Assessment Reviewdoi:10.1016/j.eiar.2026.108606
    Peer-reviewed2026-07-09

Cite this record

v1

Truvace Impact Record TRV-2026-2700, v1: “Towards trustworthy LLM-assisted EPD comparability assessment for circular construction materials.” Truvace, 2026-11-12. /record/TRV-2026-2700 (accessed on the day you copy it). sha256 c416c14efba3b128…

Change history

1 version

Every change made to this record since it was first published, and why. Nothing has changed since it went up.

  1. Publishedv1c416c14efba3…

    Certified into the record

Check this record hasn’t been altered

Check this record hasn’t been altered
How to check it yourself, without trusting this page

Download any version from /api/record/TRV-2026-2700 and hash its canonical field yourself, for example with shasum -a 256. You should get its content_hash. Each version’s text also ends with prev:and the hash of the version before it (version 1 points to 64 zeros). If anyone had changed a single character of any version after it was saved, those hashes wouldn’t line up.