Two types of people exist in the world of environmental chemistry: those who already know that predicting how long a chemical lingers in soil is a nightmare, and those who are about to find out.
The Blueprint Problem
Here's what makes predicting chemical persistence in soil such a structural disaster. You've got a molecule. You want to know how long it hangs around before soil microbes chew it up. Simple question, right? Except the answer depends on temperature, pH, soil type, microbial communities, organic carbon content, and roughly a dozen other variables that shift from one field to the next. Running the standard lab test (OECD 307, if you're keeping score) takes months, multiple soil types, and a budget that makes grad students weep.
So most chemicals? We just... don't know. Over 40% of substances registered under EU chemical regulations lack enough experimental data for even a rough persistence screening (Fenner et al., 2023). That's like approving building permits without checking if the foundation is made of sand.
Enter the Probabilistic Architect
Moritz Salz and colleagues at Eawag (Switzerland's aquatic research institute, which sounds relaxing but is anything but) decided the old approach of spitting out a single half-life number was architecturally unsound. Their solution? Don't predict a number. Predict a probability distribution (Salz et al., 2026).
Their framework, delightfully named PEPPER, uses Gaussian Process Regression - a machine learning method that's basically the colleague who says "I think it's around 40 days, but honestly I'm only 60% sure" instead of "it's exactly 37.2 days, trust me." GPR doesn't just give you an answer; it tells you how much it trusts that answer. The model was trained on 867 pesticide half-lives drawn from over 6,300 experimental observations in the enviPath database (Trostel et al., 2024).
The Load-Bearing Walls
The model's overall R-squared is 0.32. Before you spit out your coffee - yes, that's modest. The researchers know it. But here's the architectural trick that makes this building stand: when the model is confident, it's right.
By filtering predictions through confidence thresholds, users can separate the load-bearing predictions from the decorative ones. At the "good confidence" level (uncertainty below 0.5 log-days, roughly a 3-fold range), the predictions are reliable enough for regulatory screening. It's like a building inspector who says "I can't vouch for every room, but the ones I've checked are solid."
The model also outperformed the two established tools in the field - EPISuite's Biowin4 and the VEGA persistence model - on external validation. Not bad for the new kid on the block.
What's Lurking in the Basement
The team applied PEPPER to two real-world datasets and found some unsettling things hiding in the basement.
First, pesticide transformation products. When a pesticide breaks down, its fragments can themselves be persistent - sometimes more so than the parent compound. Of 819 transformation products lacking kinetic data, 493 received confident predictions, and several supposedly "minor" breakdown products showed disturbingly high persistence probabilities.
Second, they screened nearly 95,000 globally marketed chemicals. Twenty-six substances popped up with greater than 70% probability of being persistent, including fluoroquinolone antibiotics and azole antifungals. These aren't exotic lab curiosities - they're compounds flowing through hospitals and farms right now.
The Open Floor Plan
In a move that should be standard practice but somehow still feels radical, the entire framework is open. The Python library (pepper-lab) is on PyPi. The code lives on GitHub. There's even a Streamlit web app where you can punch in a molecule's SMILES string and get a persistence probability back. If you're the kind of person who enjoys mapping out complex probability landscapes visually, tools like mapb2.io pair nicely with this sort of multi-dimensional chemical assessment work.
The Verdict
PEPPER's architecture isn't flashy. The encoder has clean lines and honest load distribution. The decoder doesn't pretend to know more than it does. And that restraint - that willingness to say "I don't know" with mathematical precision - is exactly what chemical regulation needs. In a field drowning in uncertainty, the most useful thing a model can do is tell you how uncertain it is.
The EU's Safe and Sustainable by Design framework is pushing for computational persistence screening before chemicals ever get synthesized. Tools like PEPPER could let chemists check a molecule's environmental staying power the way an architect checks wind loads - early, often, and with honest error bars.
Sometimes the most confident thing you can say is how uncertain you are.
References
-
Salz, M., Cordero Solano, J.A., Fenner, K., & Hafner, J. (2026). Confidently Uncertain: Probabilistic Machine Learning to Predict Soil Biotransformation Half-Lives. Environmental Science & Technology, 60(14), 11077-11086. DOI: 10.1021/acs.est.6c03516. PMCID: PMC13085514.
-
Trostel, L. et al. (2024). Advancements in Biotransformation Pathway Prediction: Enhancements, Datasets, and Novel Functionalities in enviPath. Journal of Cheminformatics. DOI: 10.1186/s13321-024-00881-6. PMCID: PMC11304562.
-
Fenner, K. et al. (2023). Systematic Handling of Environmental Fate Data for Model Development. Environmental Science & Technology Letters. DOI: 10.1021/acs.estlett.3c00526. PMCID: PMC10569042.
-
Umeh, A. et al. (2024). Predicting Hydrocarbon Primary Biodegradation in Soil and Sediment Systems Using System Parameterization and Machine Learning. Environmental Toxicology and Chemistry, 43(6), 1352+. DOI: 10.1002/etc.5851.
-
Künnemann, L. et al. (2026). In Silico Analysis of Contaminant Persistence: From QSARs to Machine Learning Models. Environmental Science & Technology, 60(12), 8905-8922. DOI: 10.1021/acs.est.5c18542.
Disclaimer: This blog post is a simplified summary of published research for educational purposes. The accompanying illustration is artistic and does not depict actual model architectures, data, or experimental results. Always refer to the original paper for technical details.