LY75 Biologics Sequence Review Report 2026: Lymphocyte antigen 75 Similarity and Patent-Risk Signals

This LY75 Biologics Sequence Review Report was produced with PatSnap Biology Modality MCP workflows. It connects patent-scale similarity search, sequence retrieval, pairwise alignment and antibody–antigen evidence in a reproducible screen. Explore the PatSnap MCP servers used in this report.

Review date: 17 September 2026. This report supports R&D and IP triage; it is not a legal opinion, freedom-to-operate conclusion or validity analysis. A sequence hit does not establish infringement. “Claimed” is a database annotation that still requires family consolidation, live-claim review and jurisdiction-specific claim construction.

Executive sequence-risk thesis

LY75 is a protein directed to Lymphocyte antigen 75. Public therapeutic sequence data from UniProtKB/Swiss-Prot reviewed human protein record supplied the query material: Full-length protein 1722 aa. PatSnap’s all-patent protein search returned a closest review hit at 100.00% query identity across 1722/1722; the returned record was marked Yes.

The screening conclusion is elevated diligence priority, not “blocked” or “clear.” Similarity is most informative when interpreted by chain, CDR/framework location, construct architecture, target evidence and the language of live claims. Constant-region reuse or a common light chain can produce high percentages without proving asset-level collision, while a small number of substitutions in a CDR or linker junction can be disproportionately important.

Sequence scope and MCP workflow

The review began with traceable UniProtKB/Swiss-Prot reviewed human protein record query sequences. Each full-length protein query was submitted with ls_sequence_search_submit against ALLPATENT and CLAIMS protein records, allowing gaps, using E-value ≤1×10⁻³ and a 20-record task cap. Results were retrieved with ls_sequence_search_get_results; the closest informative hit was resolved with ls_sequence_fetch and compared using ls_sequence_alignment. ls_patent_sequence_fetch and ls_antibody_antigen_search supplied patent and target context.

Similarity search readout

The largest chain-level result set contained 20 records. These are search records, not unique inventions, enforceable claims or independent families. Publications can repeat the same sequence across jurisdictions, examples, comparators and continuations. Deduplication by earliest priority, applicant, simple family and legal status is required before business conclusions.

Module-level reading of the construct

The available query set contains 1 independently searchable chain module(s). For this single-pair format, heavy- and light-variable evidence should still be interpreted together. A highly conserved light chain can be shared across unrelated heavy chains, while a heavy-chain match may include common framework and constant-region sequence outside the specificity-defining CDRs.

The chain totals also provide a practical specificity check. A chain that repeatedly reaches the task cap is less discriminating at the raw-sequence level than a chain with a smaller, concentrated result set. Reviewers should therefore prioritize the rarest domain or junction, then use the more widely reused chain as corroboration. This ordering reduces the risk of treating platform-level or germline similarity as evidence of an asset-level collision.

Pairwise alignment: what the closest hit means

The selected Full-length protein query comparison reported 1722/1722 identical positions, query coverage 1722/1722, E-value 0 and 0/1722 gaps. The matched subject sequence was resolved as sequence 18539774, 1,746 aa, annotated “unnamed sequence”.

Percentage identity alone is not a claim chart. The next review should map every mismatch to IMGT/Kabat position, CDR or framework, constant region, linker boundary and any claimed SEQ ID. For multispecific assets, each arm should also be searched independently because a full-construct query can obscure highly conserved binding modules.

Antibody–antigen and patent-sequence evidence

The exact asset-name filter did not return a direct antibody–antigen relation. Because naming and alias coverage varies across patent records, the result should be supplemented with target-level and development-code searches; it must not be read as negative biological or patent evidence.

No directly named patent sequence set was resolved from the first antibody–antigen record. That absence is an evidence-coverage limitation, not evidence of patent clearance; family and alias searches remain necessary.

Evidence strength and blind spots

The evidence is strongest for the exact query sequences, the returned alignment coordinates and the patent records directly resolved by the MCP tools. It is weaker where therapeutic aliases are absent, where a publication supplies fragments instead of the administered construct, or where the result set is capped before all lower-ranked families are reviewed. Antibody names can also refer to a parental molecule, biosimilar, anti-drug antibody or comparator; the underlying sequence and target annotation must be read before attributing a record to LY75.

Patent sequence listings are deliberately broad and can contain screening libraries, consensus sequences, controls, antigens, primers and manufacturing elements alongside candidate therapeutics. Conversely, relevant claims may define a molecule through CDR combinations, percentage-identity thresholds, functional binding language or genus formulas without reproducing the exact commercial sequence. This is why the report combines sequence similarity with antibody–antigen evidence and still stops short of a legal conclusion.

Patent-risk interpretation

Diligence actions

1. Confirm that the reviewed sequence matches the clinical or commercial construct rather than an early lead or analytical reference.
2. Repeat searches for CDR-only queries, junctions and nucleotide sequences, then cluster records by patent family.
3. Annotate each high-identity hit by VH/VL domain, CDR, framework, Fc and linker position.
4. Retrieve the underlying sequence listing and verify the returned sequence number and “claimed” annotation against the filed document.
5. Build jurisdiction-specific claim charts for live families and document licenses or platform rights affecting Lymphocyte antigen 75 programs.
6. Rerun the MCP workflow at the transaction or development decision date because sequence and legal-status coverage changes.

Bottom line

LY75 has a traceable therapeutic sequence. The combination of 100.00% closest-hit identity, Yes claim annotation, and an exact-name evidence gap and 0 directly fetched patent sequences supports elevated diligence priority. The defensible outcome is a prioritized, domain-aware family and claim review—not a binary clearance statement.

Explore PatSnap Open Platform MCP Servers to produce sequence similarity and patent-risk reports for antibodies, proteins, peptides and nucleic-acid assets.

Sources and methodology notes

Query sequences: UniProtKB/Swiss-Prot reviewed human protein record. Core similarity, sequence, alignment, patent-sequence and antibody–antigen evidence was retrieved through PatSnap Biology Modality MCP on 17 September 2026. Database annotations and legal status can change; rerun at the decision date.