TruaceTracing the truth around AIWednesday, August 26, 2026
TRV-2026-0894Certified recordPeer-reviewed

Developing and evaluating automated deep learning and human-in-the-loop vision-language systems for microplastic characterization

Microplastic (MP) pollution poses escalating environmental risks, demanding efficient and reproducible tools for morphological characterization of plastic particles. Traditional manual microscopy is labour-intensive, operator-dependent, and poorly suited to large-scale monitoring. This study presents a comparative evaluation of two distinct artificial intelligence paradigms for the analysis of optical microscope images of microplastics. The first paradigm is a domain-specific, multi-task deep learning (DL) class…

Climate · G Space — documented gain · certified 2026-08-26 · v1 · article view · machine-readable

Current reading — gain

Domain-specific EfficientNet-B0 classifier and Claude Vision API with human-in-the-loop guidance automated morphological characterization of microplastics from optical microscope images, achieving high F1-scores for shape/type, color and texture.

What this doesn’t fix

Evaluation relied on a small in-house dataset of approximately 700 annotated images and VLM performance was substantially lower without expert guidance, limiting generalizability to large-scale monitoring.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-0894, v1: “Developing and evaluating automated deep learning and human-in-the-loop vision-language systems for microplastic characterization.” Truvace, 2026-08-26. /record/TRV-2026-0894 (accessed at citation time). sha256 068a458800f3bae8

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1068a458800f3

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-0894 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.