TRV-2026-2199Certified recordPeer-reviewed

pxGPT: A schema-constrained multimodal LLM framework for plant phenotyping

Summary Deep learning can scale image-based plant phenotyping but typically targets predefined traits, whereas manual phenotypic description is more flexible but difficult to scale. We present Phenotype eXplorer Generative Plant Traits (pxGPT), a Python framework that converts multi-view plant images into structured phenotype records. The workflow combines free-text description, dataset-specific schema generation with human review, and schema-constrained information extraction. We evaluated the extraction stage…

Science · The Trace — both readings · certified 2026-10-23 · v1 · article view · machine-readable

Current reading — gain

Schema-constrained extraction from multi-view images recorded visible Brassica traits without separate training per trait, with agreement close to that among human annotators.

Current reading — problem

Sensitivity varied across structure types in one mature-plant dataset, and accuracy must be validated again for each new crop or imaging setting.

What this doesn’t fix

Results are limited to the evaluated Brassica datasets, sensitivity varied by structure type in one mature-plant dataset, and accuracy must be validated for other crops and imaging conditions.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-2199, v1: “pxGPT: A schema-constrained multimodal LLM framework for plant phenotyping.” Truvace, 2026-10-23. /record/TRV-2026-2199 (accessed at citation time). sha256 20a17677ee273fee…

Calibration history

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

  1. Certifiedv120a17677ee27…

    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-2199 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.