Adverse Outcome Pathway Development II: Best Practices
Bibliographic record
Abstract
Organization of existing and emerging toxicological knowledge into adverse outcome pathway (AOP) descriptions can facilitate greater application of mechanistic data, including those derived through high-throughput in vitro, high content omics and imaging, and biomarker approaches, in risk-based decision making. The previously ad hoc process of AOP development is being formalized through development of internationally harmonized guidance and principles. The goal of this article was to outline the information content desired for formal AOP description and some rules of thumb and best practices intended to facilitate reuse and connectivity of elements of an AOP description in a knowledgebase and network context. For example, key events (KEs) are measurements of change in biological state that are indicative of progression of a perturbation toward a specified adverse outcome. Best practices for KE description suggest that each KE should be defined as an independent measurement made at a particular level of biological organization. The concept of "functional equivalence" can help guide both decisions about how many KEs to include in an AOP and the specificity with which they are defined. Likewise, in describing both KEs and evidence that supports a causal linkage or statistical association between them (ie, a key event relationship; KER), best practice is to build from and contribute to existing KE or KER descriptions in the AOP knowledgebase rather than creating redundant descriptions. The best practices proposed address many of the challenges and uncertainties related to AOP development and help promote a consistent and reliable, yet flexible approach.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.121 | 0.170 |
| Meta-epidemiology (narrow) | 0.003 | 0.002 |
| Meta-epidemiology (broad) | 0.002 | 0.004 |
| Bibliometrics | 0.021 | 0.016 |
| Science and technology studies | 0.003 | 0.008 |
| Scholarly communication | 0.020 | 0.014 |
| Open science | 0.015 | 0.010 |
| Research integrity | 0.007 | 0.010 |
| Insufficient payload (model declined to judge) | 0.006 | 0.007 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".