Skip to main content

    Paragraph outputs and interpretation

    Paratope residues, per-residue probabilities, and regions from Paragraph.

    paragraphoutputs

    Paragraph returns, per sequence, the list of predicted paratope residues, a per-residue table of position, amino acid, probability, and region, and summary counts including the mean paratope probability. Read the per-residue probabilities, not just the paratope/not-paratope call: a residue at 0.9 is a firmer "don't touch this" than one at 0.51, which matters when you're deciding which positions to hold fixed during humanization.

    Per-sequence result

    FieldTypeWhat it tells you
    sequence_namestringThe name you gave the sequence.
    chain_typestringThe chain reported (H or L).
    residue_predictionslistPer-residue predictions (see below).
    paratope_residuesstring[]Residues predicted to be part of the paratope.
    paratope_sequencestring | nullThe paratope residues concatenated.
    num_paratope_residuesintCount of predicted paratope residues.
    mean_paratope_probabilityfloat | nullMean probability across the paratope residues.

    Per-residue prediction

    Each entry in residue_predictions:

    FieldTypeWhat it tells you
    positionstringNumbered position (e.g. "31").
    residuestringAmino-acid one-letter code.
    probabilityfloatParatope probability (0–1).
    is_paratopeboolWhether it cleared the threshold.
    regionstring | nullRegion annotation (CDR-H1, FR-H2, …).

    Job-level summary

    FieldTypeMeaning
    failed_sequencesstring[]Sequences Paragraph could not predict.
    success_countintSequences predicted successfully.
    fail_countintSequences that failed.
    threshold_usedfloatProbability threshold applied.

    Reading the result card

    The Paragraph result renders on the canvas as an antibody paratope card, surfacing the binding-residue count and the per-residue probabilities so you can see the paratope at a glance.

    What to do next

    • Before running biophi_humanize, check whether its paratope overlaps the framework — if it's clean, keep binding-residue preservation on (the default) rather than naming positions, since the tool only exposes an on/off toggle.
    • Compare the paratope against Humatch's flagged low-humanness positions to avoid a conflict.
    • Use the region annotations to target a specific CDR loop for redesign.

    Was this page helpful?

    On this page

    On this page

    Loading...