Moderate evidence
Published recordLaborGood Space
More
Artificial Intelligence and Agricultural Structural Transformation: Evidence from Productivity, GDP Share, and Employment
- Truvace record
- TRV-2026-2985raw data (JSON)
- Version
- v1Published
- First published
- Evidence type
- Observational study
- Sources
- 1 sourcePeer-reviewed
- sha256
- ba3be54222ae…check it
This paper investigates the relationship between AI patent accumulation and three aspects of the agricultural sector. These are value added per worker, agriculture’s share of GDP, and the share of agricultural employment in total employment. The sample of the study includes 20 countries. Countries are observed from 1990 to 2024. A two-way panel specification including country and year fixed effects are used in the paper to estimate the regressions. Driscoll–Kraay standard errors are used for inference. The resul…
The gain
A panel study of 20 countries from 1990 to 2024 found that higher AI patent intensity was associated with higher agricultural value added per worker, though the result was statistically fragile and not shown to be causal.
What this doesn’t fix
The authors say the results should not be interpreted as evidence of a causal relationship, and the productivity and employment-share findings are statistically more fragile than the GDP-share finding.
Sources
1 on file- Black Sea Journal of Agriculturedoi:10.47115/bsagriculture.2014138
Cite this record
v1Truvace Impact Record TRV-2026-2985, v1: “Artificial Intelligence and Agricultural Structural Transformation: Evidence from Productivity, GDP Share, and Employment.” Truvace, 2026-11-17. /record/TRV-2026-2985 (accessed on the day you copy it). sha256 ba3be54222ae9a0c…
Change history
1 versionEvery change made to this record since it was first published, and why. Nothing has changed since it went up.
Certified into the record
Check this record hasn’t been altered
How to check it yourself, without trusting this page
Download any version from /api/record/TRV-2026-2985 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.
ace