rewirebio.iobenchmarks
Dataset subset

POISK binder records with mappable patent epitope annotations (1,232)

The benchmark binder records whose patent-reported epitope residues could be mapped onto the folded antigen construct, used to test where the models place the antibody.

Evaluation results

6 evaluations · 6 results. Different protocols are not a single leaderboard.

Filter evaluations

Applied filters: All linked evaluations

Exact evaluated configurations and original reported results
Tested configurationProtocol and datasetFindingEvidence and details
Configuration: AlphaFold-Multimer with full-Fv ipSAE rankingProtocol: POISK epitope contact recovery
Dataset subset: POISK binder records with mappable patent epitope annotations (1,232)
50.4% Success rate (at least one annotated epitope residue with a heavy atom within 4 angstrom of an antibody heavy atom, over 1,232 binder records with mappable patent epitope annotations)
percent · higher

Uncertainty: Not reported by the source: Table 2 prints a single percentage per engine with no spread.

Coverage: 1232/1232 binder records with mappable patent epitope annotations scored

Author-reported evaluation · Source checked
Methods, coverage and source

AlphaFold-Multimer on POISK epitope contact recovery

poisk-20261115-protocol-epitope-recovery

Aggregation: Not reported

Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF) · Table 2, row "AlphaFold-Multimer", column "Epitope Recovery Records (%)"
Configuration: Boltz-2 with full-Fv ipSAE rankingProtocol: POISK epitope contact recovery
Dataset subset: POISK binder records with mappable patent epitope annotations (1,232)
55.4% Success rate (at least one annotated epitope residue with a heavy atom within 4 angstrom of an antibody heavy atom, over 1,232 binder records with mappable patent epitope annotations)
percent · higher

Uncertainty: Not reported by the source: Table 2 prints a single percentage per engine with no spread.

Coverage: 1232/1232 binder records with mappable patent epitope annotations scored

Author-reported evaluation · Source checked
Methods, coverage and source

Boltz-2 on POISK epitope contact recovery

poisk-20261115-protocol-epitope-recovery

Aggregation: Not reported

Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF) · Table 2, row "Boltz-2", column "Epitope Recovery Records (%)"
Configuration: IntelliFold v2 with full-Fv ipSAE rankingProtocol: POISK epitope contact recovery
Dataset subset: POISK binder records with mappable patent epitope annotations (1,232)
56.5% Success rate (at least one annotated epitope residue with a heavy atom within 4 angstrom of an antibody heavy atom, over 1,232 binder records with mappable patent epitope annotations)
percent · higher

Uncertainty: Not reported by the source: Table 2 prints a single percentage per engine with no spread.

Coverage: 1232/1232 binder records with mappable patent epitope annotations scored

Author-reported evaluation · Source checked
Methods, coverage and source

IntelliFold v2 on POISK epitope contact recovery

poisk-20261115-protocol-epitope-recovery

Aggregation: Not reported

Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF) · Table 2, row "IntelliFold v2", column "Epitope Recovery Records (%)"
Configuration: OpenFold3 with full-Fv ipSAE rankingProtocol: POISK epitope contact recovery
Dataset subset: POISK binder records with mappable patent epitope annotations (1,232)
52.4% Success rate (at least one annotated epitope residue with a heavy atom within 4 angstrom of an antibody heavy atom, over 1,232 binder records with mappable patent epitope annotations)
percent · higher

Uncertainty: Not reported by the source: Table 2 prints a single percentage per engine with no spread.

Coverage: 1232/1232 binder records with mappable patent epitope annotations scored

Author-reported evaluation · Source checked
Methods, coverage and source

OpenFold3 on POISK epitope contact recovery

poisk-20261115-protocol-epitope-recovery

Aggregation: Not reported

Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF) · Table 2, row "OpenFold3", column "Epitope Recovery Records (%)"
Configuration: Protenix-v1 with full-Fv ipSAE rankingProtocol: POISK epitope contact recovery
Dataset subset: POISK binder records with mappable patent epitope annotations (1,232)
58.9% Success rate (at least one annotated epitope residue with a heavy atom within 4 angstrom of an antibody heavy atom, over 1,232 binder records with mappable patent epitope annotations)
percent · higher

Uncertainty: Not reported by the source: Table 2 prints a single percentage per engine with no spread.

Coverage: 1232/1232 binder records with mappable patent epitope annotations scored

Author-reported evaluation · Source checked
Methods, coverage and source

Protenix-v1 on POISK epitope contact recovery

poisk-20261115-protocol-epitope-recovery

Aggregation: Not reported

Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF) · Table 2, row "Protenix-v1", column "Epitope Recovery Records (%)"
Configuration: Protenix-v2 with full-Fv ipSAE rankingProtocol: POISK epitope contact recovery
Dataset subset: POISK binder records with mappable patent epitope annotations (1,232)
62.8% Success rate (at least one annotated epitope residue with a heavy atom within 4 angstrom of an antibody heavy atom, over 1,232 binder records with mappable patent epitope annotations)
percent · higher

Uncertainty: Not reported by the source: Table 2 prints a single percentage per engine with no spread.

Coverage: 1232/1232 binder records with mappable patent epitope annotations scored

Author-reported evaluation · Source checked
Methods, coverage and source

Protenix-v2 on POISK epitope contact recovery

poisk-20261115-protocol-epitope-recovery

Aggregation: Not reported

Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF) · Table 2, row "Protenix-v2", column "Epitope Recovery Records (%)"

Source checking is not independent reproduction. Release 2026-11-21-c8bea25e5abb.

Research readiness

0 of 4 readiness checks met. These checks assess whether the evidence supports a reproducible investigation; a source-checked score alone does not meet them.

Readiness checks, gaps and artifacts

Release 2026-11-21-c8bea25e5abb · Evidence verified: Not verified

Evidence incomplete

Replay metrics

Exact outcomes, predictions, identifiers and evaluator are connected.

Missing or unresolved evidence

  • No verified artifact manifest is linked to this exact record.
  • File checksums match the recorded files: not yet verified
  • Predictions are matched to the right samples: not yet verified
  • Score meaning and direction are confirmed: not yet verified
  • Metrics are recomputed from the saved predictions: not yet verified

Verified: Not verified

Evidence incomplete

Investigate discrepancies

Replay evidence includes annotations and an assessment of dependence. Unknown independence permits descriptive analysis only.

Missing or unresolved evidence

  • No verified artifact manifest is linked to this exact record.
  • File checksums match the recorded files: not yet verified
  • Predictions are matched to the right samples: not yet verified
  • Score meaning and direction are confirmed: not yet verified
  • Metrics are recomputed from the saved predictions: not yet verified
  • Sample annotations are recorded: not yet verified
  • Dependence between samples is assessed: not yet verified

Verified: Not verified

Evidence incomplete

Run locally

A pinned recipe describes the inputs, environment and resource requirements.

Missing or unresolved evidence

  • No verified artifact manifest is linked to this exact record.
  • File checksums match the recorded files: not yet verified
  • Predictions are matched to the right samples: not yet verified
  • Score meaning and direction are confirmed: not yet verified
  • A pinned run recipe exists: not yet verified
  • Compute requirements are estimated: not yet verified

Verified: Not verified

Evidence incomplete

Validate independently

Separate data and exposure records support an independent test.

Missing or unresolved evidence

  • No verified artifact manifest is linked to this exact record.
  • File checksums match the recorded files: not yet verified
  • Predictions are matched to the right samples: not yet verified
  • Score meaning and direction are confirmed: not yet verified
  • Independent validation data exist: not yet verified
  • Overlap with training data is checked: not yet verified

Verified: Not verified

Readiness describes the evidence in this release. Availability on your computer is checked separately when an investigation runs. Existing data exposure can prevent independent validation even when files are available.

Artifacts and reproduction

No verified artifact manifest is connected to this record yet. The gaps above identify what is needed before analysis can begin.

Subset and evaluation context

This record describes a particular subset or cohort used in an evaluation. Its results do not describe the full dataset.

Evidence

Source checking verifies the cited claim or transcription. It does not establish independent reproduction.

Evidence table

Inspect claims, sources and review details

Trace each statement to its source and review. A context-only reference supports the record generally; it does not verify an individual field. Source checking does not reproduce an experiment.

One row per statement and cited source. Multiple citations are not independent evaluations. Shared locators are labelled explicitly.

11 evidence rows matching the loaded filters

Claims, original sources and review scope · Release 2026-11-21-c8bea25e5abb
Property and statementOriginal source and locationReview and provenance
Limitations
1 values
  • The reference epitope is a patent text annotation, not an experimentally resolved interface.
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.limitations

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Source dataset
poisk-20261115-data-cofolding-benchmark-22494
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.source_dataset

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Source location
Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.source_locator

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Split
Evaluation only
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.split

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Subset scope
The 1,232 binder records of the benchmark carrying residue-level epitope annotations (a linear range or explicit contact residues) that could be mapped to the folded antigen construct.
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.subset_scope

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Test count
1232
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.test_count

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Version
As described in bioRxiv v1 Section 3.3.2
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: attributes.version

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Description
The benchmark binder records whose patent-reported epitope residues could be mapped onto the folded antigen construct, used to test where the models place the antibody.
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: description

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Relationship: same data as
poisk-20261115-data-cofolding-benchmark-22494
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: links:same_data_as:poisk-20261115-data-cofolding-benchmark-22494

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

Relationship: used in
poisk-20261115-benchmark-binder-decoy
Context-only references
Tupikina et al. 2026, Can Folding Models Tell Binders from Bluffers? Evidence from POISK (bioRxiv v1 PDF)

Original source ↗

Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Version: v1, posted 26 October 2026
Retrieved: 2026-11-15T23:32:24Z

not individually reviewed

No individual claim review recorded

Audit details

Field: links:used_in:poisk-20261115-benchmark-binder-decoy

Source artifact SHA-256: 526def150fb5ae8f9ac4533efcf16c86e547e636cdb9bfba9a574cd1e2a2f924

Hash scope: One download of 2026-11-15. The PDF container is not byte-stable: bioRxiv regenerates it on request, so artifact_sha256 is that one download's hash and no refetch reproduces it. Three downloads on 2026-11-16 gave 3389c1bf6d3654c5b2151a07fcfcefc67cf6f36e5f0facfc03c33521d8b84491 twice and d699fd680e3b0097ca80130c288e8d872773dc1e523044f4605e06fc4f89d9bc once. All three yield the same pdftotext -layout text layer, SHA-256 e75c18130ca43770d2f0ed05ae96528759666c0e4fa08f7725f5a32b21187696, which is the article's stable identity, is archived gzipped in artifacts/biorxiv-v1-layout.txt.gz under archive_sha256, is what extract/build_batch.py asserts, and is what every stored value was read from.

Format: application/pdf, 16 pages

How to read the evidence

Sources and history

Release 2026-11-21-c8bea25e5abb · Record review: source checked

1 source record and release historyDownload this release (gzip)
Technical metadata and record identifiers

Technical metadata for this record is tracked under stable ID poisk-20261115-data-epitope-annotated-1232.

Source locator: Section 3.3.2; Appendix C Table 5 row '+ residue-level epitope (linear range or explicit contact residues)'

Related records

Suggest a correction