Biology-Instructions
A multi-omics sequence-instruction suite with 21 formal predictive tasks across DNA, RNA, protein, and multi-molecule inputs; the final paper reports task-specific held-out evaluations rather than a single aggregate score.
Scientific task · Sequence and regulation
Epigenetic-mark prediction
Predict DNA methylation
表观遗传标记预测
Definition and search aliases
- Permanent ID
epigenetic-mark-prediction- Aliases
- chromatin mark prediction
- Deprecated aliases
- None
- Hierarchy
- Leaf task under DNA regulation and perturbation
Coverage
2 benchmark families cover this task
Biology-Instructions Epigenetic Marks Prediction
Binary prediction of whether a DNA sequence carries an epigenetic mark, evaluated with Matthews correlation coefficient.
Genomic Benchmarks
A versioned collection of nine DNA sequence-classification datasets covering regulatory elements, promoters, enhancers, open chromatin, species, and coding-context discrimination.
Evidence-backed count claims
Each row keeps its original unit and basis. Rows with different units or overlapping mappings are never added.
| Benchmark | Mapped task | Coverage | Count | Version | Evidence |
|---|---|---|---|---|---|
| Biology-Instructions root: bioinstruction | Epigenetic-mark prediction official-track · high | explicitly-in-scope | 1 tracks Formal evaluation tracks (Epigenetic Marks Prediction). | emnlp-2025 | bioinstruction-evidence-paper |
| Biology-Instructions Epigenetic Marks Prediction root: bioinstruction | Epigenetic-mark prediction official-track · high | explicitly-in-scope | 287367 examples distinct examples across the published train, validation, and test splits | emnlp-2025 | bioinstruction-emp-evidence-paper |
| Genomic Benchmarks root: genomic-benchmarks | Epigenetic-mark prediction official-taxonomy · high | explicitly-in-scope | 1 tasks Benchmark dataset classification tasks. | package-1.0.0-snapshot as of 2026-07-22 | genomic-benchmarks-paper-definition-evidence |
Official evaluations connected to these benchmarks
Runs are included only for benchmark records mapped here (and formal child tracks when a mapped suite is the root). A task mapping does not imply that every run isolates this task.