Oncofusion

start / graph / gene-ring1

Proteinmoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q50-prc1-myc

RING1 (RING1A) - the paralogue that is not RING1B, and the reason a substring search for 'RING1' in this graph returns the wrong gene

also called RING1 · RING1A · RNF1 · Polycomb complex protein RING1

RING1 is the twin of the better-known Polycomb enzyme RING1B, and the two do the same chemical job so well that removing just one of them changes almost nothing. The trap this entry exists to close is a naming one: RING1B is not this gene - it is a gene called RNF2 - so a paper or a search that says 'RING1' may mean either, and telling them apart matters because the published leukaemia experiments removed both at once.

The same thing, for a scientist

RING1 (Q06587, 406 aa, primary gene name RING1, UniProt entry name RING1_HUMAN) is one of the two interchangeable RING-domain E3 ubiquitin ligases that form the catalytic core of every PRC1 complex, canonical and variant, including PRC1.1. Its paralogue is **RNF2** (Q99496, 336 aa, entry name RING2_HUMAN), whose protein is universally called **RING1B** in the literature. The two are functionally redundant for H2AK119ub deposition, which is why the decisive leukaemia genetics deleted **both** [E1]: Ring1a/Ring1b double depletion in mice shows PRC1 activity and H2AK119ub are required for the leukaemogenic potential of Hox-activating and non-Hox-activating fusions alike. RING1 is separately named as a hit in an EZH2-inhibition-anchored genome-wide CRISPRi screen in GCB-DLBCL alongside USP7, KDM2B and PCGF1 [E2], which is the clearest published instance of RING1 rather than RNF2 being the gene under test. The only haematological-malignancy expression data this beat located for RING1 specifically is an MDS/AML expression series reporting RING1 overexpression with adverse prognostic scoring [E3] - a transcript-level association in a non-KMT2A population, and it is weak. **There is no published RING1-specific (as opposed to RNF2-specific or double-knockout) experiment in KMT2A-rearranged leukaemia**, a bounded absence recorded in `ana-prc1-myc-enumeration-and-bounded-absences`.

What it looks like
loading AF-Q06587-F1…
AlphaFold AF-Q06587-F1 ↗
colourshape

This is a prediction, not a measurement. No one has seen this protein in this shape. The colours say how much the software trusts itself, and that is worth reading before anything else — the orange stretches are places the model is effectively saying this part has no fixed shape.

very high (90+)confident (70–90)low (50–70)very low (<50)
I have never read one of these pictures before

A protein is one long chain of amino acids that folds up. The ribbon traces that chain from one end to the other; it is not a wire, it is a simplification of where the backbone runs. Drag to rotate, scroll to zoom.

Domains are the stretches of chain that do a particular job, and they are what the coloured blocks above the picture mark out. Click one and the view flies to it. In this project the important question about any domain is usually whether the fusion still has it — the labels say lost where it does not.

Anything in yellow sticks is a bound small molecule, which is usually the drug.

Go deeper
The identifier trap, stated precisely

Fetched from UniProt on 2026-09-20, gene_exact:<symbol> AND organism_id:9606 AND reviewed:true, one reviewed record each, primary gene name read back:

askedaccessionentry nameprimary genesynonymslengthprotein name contains
RING1Q06587RING1_HUMANRING1RING1A, RNF1406RING finger protein 1
RNF2Q99496RING2_HUMANRNF2BAP1, DING, HIPI3, RING1B336RING finger protein 1B

Three separate failure modes follow.

1. The substring artefact. RING1 is a strict prefix of RING1B. A plain substring count of RING1 over this graph's 1,510 node files does not distinguish them; the word-boundary counts run on 2026-09-20 give \bRING1B\b = 7 entries and \bRING1A\b = 6. This is the same class of error as the BENC substring artefact the coordinator found in this beat's own dispatch brief, where a substring search suggested 79 entries and the word-boundary count was zero.

2. The entry-name inversion. The gene RNF2 has the UniProt entry name RING2_HUMAN while its protein is called RING1B. So a reader who resolves RING1B and reads back RING2_HUMAN sees a number that does not match and may conclude the lookup failed. It did not. This is a fresh instance of brief rule 65's family: reading the record back does not, on its own, settle it.

3. Length is a genuine defence here, unlike in the RAS family. 406 against 336 is a 70-residue gap, well outside the ambiguous band that rule 68 documents for KRAS/NRAS/HRAS (0 aa) and rule 66 for SMC1A/SMC3 (16 aa). Assert accession and length_aa and verify-accessions.py will catch a swap.

And rule 65's protein-name defence does work in this case, which is worth recording because it usually is the step that fails: RNF2's protein name contains RING finger protein 1B and RING1's contains RING finger protein 1. A reader asking 'is this RING1B?' gets the right answer from either record. The defence that fails is the search, not the read-back.

What RING1 does, and how little of it has been separated from RNF2

RING1 and RING1B are alternative occupants of the same slot: each supplies the RING-domain E3 activity that monoubiquitinates histone H2A at K119, and each partners a PCGF paralogue that sets the complex's flavour (PCGF1 for PRC1.1). Because they substitute for one another, single-gene perturbations are close to uninformative and the leukaemia literature reflects that - Rossi et al. depleted Ring1a and Ring1b to see a phenotype at all 1.

The consequence for this graph is specific. gene-rnf2 carries the sentence 'catalytic subunit of ALL PRC1 complexes'; that is correct but incomplete, because the catalytic function is shared with this gene and every mouse genetic result in this project's PRC1 evidence base is a double loss. Any claim of the form 'RING1B is required for X in leukaemia' derived from Rossi et al. is, strictly, a claim about the RING1A/RING1B pair. mechanism-h2ak119ub-is-a-double-knockout-result is not written; the qualification lives here and in this entry's caveats.

The Göbel screen 2 is the useful exception in the other direction: a genome-wide CRISPRi screen in GCB-DLBCL names RING1 (not RNF2) among ncPRC1 components whose loss modifies EZH2-inhibitor sensitivity, alongside USP7, KDM2B and PCGF1. That is an instance of RING1 carrying non-redundant weight in a chromatin-drug context, in a B-lineage malignancy - the closest available analogue to the lymphoid arm of this project's disease, and still not the disease.

Polycomb bodies, and why the UniProt speckle term is not adopted (Q87, 2026-09-21)

Subcellular. Nucleus (UniProt Q06587); HPA v25.1 IF nucleoplasm main, cytosol additional, reliability Approved.

Subnuclear: POLYCOMB BODIES. Tagged RING1 forms foci in human U2OS cells whose internal FRAP recovery is substantially slower than the surrounding nucleoplasm (PMID 24460908). PcG bodies overlie pericentric heterochromatin, and PRC1 recruitment to them requires the PRC2 members EED and EZH2 and the maintenance methyltransferase DNMT1 (PMID 16314526) - so this address is conditional on PRC2, which matters for any EZH2/EED-inhibitor experiment.

The UniProt 'Nucleus speckle' term is flagged, not adopted. It rests solely on PMID 21282530, an interaction-proteomics paper with no imaging in its abstract, and RING1[tiab] AND ("nuclear speckle"[tiab] OR "nuclear speckles"[tiab]) returns 0. Rule 91: ECO:0000269 means a curator read AN experiment, not THE experiment.

Cell type and state. Leukaemic cell identity in mouse, functionally, via Ring1a/Ring1b double depletion - a PRC1 statement, not a RING1 one. No PcG body has ever been imaged in a blast.

Shown for fusion. MLL-AF9-class Hox-activating fusions for function; nobody for localisation.

Facts and figures
uniprotQ06587
length AA406
gene primaryRING1
protein nameE3 ubiquitin-protein ligase RING1
uniprot entry nameRING1_HUMAN
alphafold IDAF-Q06587-F1
accession resolutionUniProt REST gene_exact:RING1 AND organism_id:9606 AND reviewed:true, run 2026-09-20; exactly one reviewed row; gene_primary read back as RING1 and length 406 taken from the same fetched record.
complexcatalytic E3 of all PRC1 flavours, redundant with RNF2/RING1B
catalytic activityE3 ubiquitin ligase depositing H2AK119ub1
kmt2a specific evidencenone found; every leukaemia result in this graph's PRC1 evidence base is a Ring1a/Ring1b DOUBLE loss
gene symbolRING1
gene symbol notepromoted from gene_primary 2026-09-20: verify-accessions.py reads data.gene_symbol, so a gene_primary-only entry was being length-checked or id-inferred rather than symbol-asserted
subnuclear localizationPOLYCOMB BODIES. Tagged RING1 forms nuclear foci in human U2OS cells whose internal FRAP recovery is substantially slower than the surrounding nucleoplasm, marking them as a kinetically distinct compartment (PMID 24460908); PcG bodies overlie pericentric heterochromatin and require PRC2 (EED, EZH2) for PRC1 recruitment (PMID 16314526). UniProt's competing 'Nucleus speckle' term is NOT adopted here: it rests on an interaction-proteomics paper that reports no imaging, and RING1[tiab] AND ("nuclear speckle"[tiab] OR "nuclear speckles"[tiab]) returns 0 records.
cell stateLEUKAEMIC CELL IDENTITY, in the sense of the Rossi et al. title - the state that collapses when PRC1 catalysis is removed. Note the paralogue caveat: the state result is Ring1a/Ring1b double depletion, so it is a PRC1 statement and not a RING1 statement.
shown for fusionMLL-AF9-class Hox-activating fusions for FUNCTION (mouse, Ring1a/Ring1b double depletion); NOBODY for LOCALISATION. Measured 2026-09-21: (RING1[tiab] OR RING1A[tiab] OR RNF1[tiab]) AND the eight-term fusion clause AND the ten-term localisation clause returns 0 records. No PcG body has been imaged in a KMT2A-rearranged cell.
graph word boundary counts 2026 09 20
RING1A6.000RING1A: 6RNF26.000RNF2: 6RING1B7.000RING1B: 7
gene synonyms
[
  "RING1A",
  "RNF1"
]
paralogue
{
  "gene": "RNF2",
  "protein_called": "RING1B",
  "uniprot": "Q99496",
  "uniprot_entry_name": "RING2_HUMAN",
  "length_aa": 336,
  "graph_node": "gene-rnf2",
  "length_gap_aa": 70,
  "length_is_a_reliable_discriminator": true
}
identifier traps
[
  "'RING1' is a strict substring of 'RING1B' - any substring count conflates the two genes; use word boundaries",
  "the gene RNF2 has UniProt entry name RING2_HUMAN while its protein is called RING1B, so a read-back of the entry name looks like a failed lookup",
  "'RING1A' is a synonym of RING1, not a separate gene"
]
graph word boundary counts 2026 09 20 — the numbers behind the chart
{
  "RING1B": 7,
  "RING1A": 6,
  "RNF2": 6
}
depmap kmt2a selectivity
{
  "chronos_mean_kmt2a_rearranged": -0.1261,
  "chronos_mean_other_leukaemia": -0.1871,
  "difference": 0.061,
  "pan_essentiality_all_lines": -0.1748,
  "selectivity_rank": 15518,
  "rank_denominator": 17728,
  "provenance": "Joined 2026-09-21 from analyses/depmap-kmt2a-selective-scan-full (generated 2026-09-19T10:12:06Z), the project's own genome-wide scan over 11 KMT2A-rearranged and 43 other leukaemia DepMap lines. NOT re-fetched and NOT independent of that scan: every caveat it carries applies here, including that the KMT2A-rearranged arm is a small number of lines drawn from nine individuals, that the rank denominator is 17,728 genes, and that a difference is not a dependency. Added because only 26 of 308 gene entries carried this number, which made any KMT2A-selectivity question answerable for 8% of the corpus.",
  "how_to_read": "A negative difference means MORE required in KMT2A-rearranged lines than in other leukaemia lines. A rank near 17,728 is ANTI-selective. Neither is evidence of a fusion-driven dependency on its own: check pan_essentiality_all_lines before calling anything selective, and note that a paralogue-redundant gene can score near zero for reasons that have nothing to do with this disease - see ana-the-paralogue-redundancy-excuse-is-not-tested-and-my-proxy-decided-the-answer."
}
localization
{
  "subcellular": "NUCLEUS. UniProt Q06587 lists two terms, 'Nucleus' and 'Nucleus speckle', both on ECO:0000269 PubMed:21282530. HPA v25.1 IF, reliability Approved, gives Nucleoplasm as the main location with Cytosol additional.",
  "subnuclear": "POLYCOMB BODIES (PcG bodies), not speckles. Fluorescently tagged RING1, alongside the CBX proteins and BMI1, forms nuclear foci of differing size and intensity in human U2OS cells, and FRAP shows recovery INSIDE those foci is substantially slower than the diffusion-plus-transient-binding behaviour seen in the surrounding nucleoplasm - so the foci are a kinetically distinct compartment and not a staining artefact (PMID 24460908). Independently, PcG bodies are described as sitting on regions of PERICENTRIC HETEROCHROMATIN, and PRC2 members EED and EZH2 are required for BMI1 recruitment to them, which makes the compartment a PRC2-dependent PRC1 address rather than a free-standing structure (PMID 16314526).",
  "uniprot_speckle_call_is_doubtful_rule_91": "UniProt's 'Nucleus speckle' term for RING1 rests entirely on PubMed:21282530, a tandem-affinity-purification/MS-MS interaction-proteomics study of PRC1 complexes whose abstract describes NO imaging experiment at all. And the literature does not corroborate it: RING1[tiab] AND (\"nuclear speckle\"[tiab] OR \"nuclear speckles\"[tiab]) returns 0 records (2026-09-21). This is the rule-91 pattern exactly - ECO:0000269 tells you a curator saw an experiment somewhere in that paper, not that the paper is about your fact. This entry records POLYCOMB BODIES as the subnuclear answer and flags the speckle term as unsupported by any retrievable speckle literature.",
  "how_shown": "fluorescent tagging, focus morphometry and FRAP with kinetic decomposition in human U2OS cells (PMID 24460908); FRAP of BMI1 at PcG bodies with genetic dependence on EED, EZH2 and DNMT1 (PMID 16314526)",
  "tissue_of_evidence": "U2OS osteosarcoma and other non-haematopoietic human lines. No PcG-body imaging exists in any leukaemic blast, let alone a KMT2A-rearranged one.",
  "node": "localization-polycomb-bodies-kmt2a-r"
}
cell type
{
  "haematopoietic_answer": "LEUKAEMIC CELLS in mouse, functionally, and NOT by imaging. Genetic depletion of both Ring1a and Ring1b shows PRC1 activity and H2AK119ub maintain leukaemic cell identity for Hox-activating (MLL-AF9 class) and non-Hox-activating fusions alike - already recorded in this entry as E1. That is a requirement measurement, not a localisation one, and it cannot be attributed to RING1 specifically because the experiment removes both paralogues.",
  "cells_actually_imaged": "human U2OS osteosarcoma cells; no haematopoietic cell of any kind.",
  "expression_atlas": "HPA v25.1: RNA tissue specificity Low; IF reliability Approved."
}
How this could bite us back
  • A RING1B-selective inhibitor would be phenocopied away by RING1, because the two are redundant for H2AK119ub deposition - any PRC1-catalytic drug programme has to hit both, which widens the on-target footprint to every PRC1 flavour including those required for normal haematopoiesis.
  • Conversely, a dual RING1/RING1B inhibitor removes the machine through which a menin inhibitor silences its targets, so it is a candidate pharmacological antagonist of menin inhibition rather than a partner for it.
  • Because the disease-relevant genetics are double knockouts, any biomarker built on one of the two genes will be uninterpretable in a patient where the other is intact.
Still open
  1. Is RING1 non-redundant with RNF2 anywhere in KMT2A-rearranged leukaemia? No single-gene RING1 perturbation in this disease was found; every result is a double loss, so the question has not been asked rather than answered.
  2. Does the RING1 hit in the GCB-DLBCL CRISPRi screen reproduce in a B-lineage KMT2A-rearranged line? That is the cheapest test of whether RING1 carries independent weight in a lymphoid chromatin-drug context.
  3. Do RING1 and RING1B partition between PRC1 flavours - is one of them the preferred catalytic subunit of PRC1.1 specifically? A PCGF1 immunoprecipitation blotted for both would answer it in a day and would tell this project which gene its PRC1.1 claims are really about.
Every source behind this entry (7)
  1. E1strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    Genetic depletion of both Ring1a and Ring1b - the two H2A ubiquitin ligase subunits of PRC1 - is what was required to show that PRC1 activity and H2AK119 monoubiquitination support the leukaemogenic potential of Hox-activating and non-Hox-activating fusion proteins in mice.

    Maintenance of leukemic cell identity by the activity of the Polycomb complex PRC1 in mice. · Rossi A, Ferrari KJ, Piunti A, Jammula S, Chiacchiera F, Mazzarella L, et al. · Sci Adv 2016
    What this evidence cannot show

    Mouse. The double depletion is the point and also the limitation: it removes every PRC1 flavour simultaneously, so it attributes nothing to RING1 specifically and nothing to PRC1.1 specifically. The fusions studied are Hox-activating (MLL-AF9 class) and non-Hox-activating, not KMT2A::AFF1.

    Evidence that argues against this (1)
    • The therapeutic sign is reversed for the PRC1.1 flavour in KMT2A-rearranged AML under drug: loss of PCGF1 or BCOR confers menin-inhibitor resistance rather than impairing the leukaemia. A conclusion that 'PRC1 sustains the leukaemia' therefore cannot be carried to 'inhibiting PRC1 would treat it'. Zhou X et al. 2024
  2. E2moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    An EZH2-inhibition-anchored genome-wide CRISPR interference screen in germinal-centre B-cell-like DLBCL identified multiple genes encoding non-canonical PRC1 components, including USP7, KDM2B, RING1 and PCGF1.

    DOT1L Shapes ncPRC1-Target Gene Repression to Maintain Germinal Center B Cell Identity of Diffuse Large B cell Lymphoma. · Gobel C, Niccolai R, Gregoricchio S, de Groot MHP, Kneefel SFK, Kreft M, et al. · Blood 2026
    What this evidence cannot show

    GCB-DLBCL, not leukaemia, and the screen is anchored on EZH2 inhibition rather than on a menin or DOT1L inhibitor. Read at abstract level for this entry, so the effect size and direction for RING1 individually are not established here - only that the gene was called as a hit. A CRISPRi screen hit is a modifier, not a demonstration of non-redundancy with RNF2, because RNF2 may simply not have scored in that library or that context.

    Evidence that argues against this (1)
    • Redundancy is the default expectation for this pair: the mouse leukaemia genetics required double Ring1a/Ring1b depletion to produce a phenotype at all, so a single-gene RING1 hit in one screen is not by itself evidence that RING1 carries non-redundant function, and could reflect library or context-specific sensitivity. Rossi A et al. 2016
  3. E3weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper

    RING1, together with EZH2 and BMI1, is overexpressed in myelodysplastic syndromes and AML relative to non-clonal cytopenias, and its overexpression associates with poor prognostic scoring; decitabine treatment reduced EZH2 and RING1 expression.

    What this evidence cannot show

    Transcript-level expression association in MDS/AML, 2011, with no KMT2A-rearranged subgroup and no functional perturbation. Graded weak because an expression difference against a non-clonal-cytopenia comparator is confounded by blast fraction, and the decitabine effect on RING1 is an observation in treated patients, not a mechanism. Cited to bound the RING1-specific haematological literature, not to support a claim about this disease.

    Evidence that argues against this (1)
    • No published counter-study of this specific association was found by this beat. Recorded as an unopposed weak claim rather than a supported one: the absence of a contradicting paper here reflects that almost nobody has measured RING1 separately from RNF2 in myeloid malignancy, not that the finding has been tested and held. The structural point stands against it - RING1 and RING1B are redundant, so a RING1 transcript difference has no established functional interpretation. Rossi A et al. 2016
  4. E4established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    UniProt reviewed human record: RING1 is Q06587, entry name RING1_HUMAN, primary gene name RING1, synonyms RING1A and RNF1, 406 aa, recommended protein name 'E3 ubiquitin-protein ligase RING1' with alternative names 'Polycomb complex protein RING1' and 'RING finger protein 1'; the paralogue RNF2 is Q99496, entry name RING2_HUMAN, 336 aa, alternative name 'RING finger protein 1B'.

    What this evidence cannot show

    A database fact, fetched 2026-09-20. It is opposable on scope but not on content: it states what the curated record says today and nothing about how any individual paper used the string 'RING1'. Papers published before the RING1A/RING1B convention stabilised may use either spelling for either gene, and no lookup resolves an ambiguous source document.

    Evidence that argues against this (1)
    • The database cannot disambiguate the primary literature. Brief rule 66 documents the worst version of this in the family this graph is about - KMT2B and KMT2D each carry BOTH the MLL2 and MLL4 aliases and each protein name carries the other's number - and establishes that when a paper's usage is ambiguous the correct outcome is to record it unresolved rather than to resolve it from the database. Xu F et al. 2011
  5. E5moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    Fluorescently tagged RING1, together with the CBX proteins and BMI1, accumulates in nuclear foci - Polycomb bodies - in human U2OS cells, and FRAP separates two behaviours: outside the foci PcG dynamics is governed by diffusion as complexes plus transient binding, while recovery inside the foci is substantially slower and the slow-binding amplitudes scale with focus size and intensity. The foci are therefore a kinetically distinct subnuclear compartment, which is the strongest subnuclear statement available for RING1.

    PRC1 components exhibit different binding kinetics in Polycomb bodies. · Vandenbunder B, Fourré N, Leray A, Mueller F, Völkel P, Angrand PO, et al. · Biol Cell 2014
    What this evidence cannot show

    Human U2OS osteosarcoma cells with fluorescently TAGGED constructs, so the foci are reported for an exogenous protein at non-endogenous levels - the condensate-evidence caution applies, and FRAP recovery on its own cannot distinguish a phase-separated body from binding to spatially clustered sites. Nothing haematopoietic. The paper does not separate RING1 from RNF2/RING1B behaviourally.

    Evidence that argues against this (1)
    • Polycomb bodies are not a free-standing address that RING1 chooses; the compartment is built upstream of PRC1 and can be dismantled by perturbing the other complex. PcG bodies overlie regions of PERICENTRIC HETEROCHROMATIN, and the PRC2 members EED and EZH2 - plus the maintenance DNA methyltransferase DNMT1 - are required for BMI1 recruitment to them. So 'RING1 localises to Polycomb bodies' is conditional on PRC2 and on DNA methylation, and in a cell where PRC2 is perturbed - which is exactly the situation under an EZH2 or EED inhibitor - the address may not exist. An entry that records the focus without the dependency would predict the wrong result from a PRC2-inhibitor experiment. Hernández-Muñoz I et al. 2005
  6. E6moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    UniProt Q06587's 'Nucleus speckle' term for RING1 should not be relied on. It rests on a single coded citation, PubMed:21282530, which is a tandem-affinity-purification and MS/MS interaction-proteomics study defining PRC1 complexes and whose abstract describes no imaging experiment; and no speckle literature corroborates it - RING1[tiab] AND ("nuclear speckle"[tiab] OR "nuclear speckles"[tiab]) returns 0 records (2026-09-21).

    Interaction proteomics analysis of polycomb proteins defines distinct PRC1 complexes in mammalian cells. · Vandamme J, Völkel P, Rosnoblet C, Le Faou P, Angrand PO · Mol Cell Proteomics 2011
    What this evidence cannot show

    This is a criticism of a database annotation made from the cited paper's ABSTRACT plus a literature bound, not from the paper's figures - the study may well contain a localisation panel that the abstract does not mention, which is precisely the rule-80 blind spot. The claim made here is therefore the narrow one: the speckle term is not supported by anything retrievable, so it should not be quoted as RING1's subnuclear address. It is not a claim that RING1 is absent from speckles.

    Evidence that argues against this (1)
    • Against treating this as a defect in UniProt: an ECO:0000269 code does not promise that the cited paper's headline is your fact, only that a curator read an experiment in it, and this graph's own rule 91 documents four cases of exactly that on its central proteins. The more useful reading is that the speckle term and the Polycomb-body result are not necessarily in conflict - a protein can be in both - and the reason to prefer Polycomb bodies here is not that the speckle call is false but that the PcG-body result is reproducible, quantified by FRAP, and mechanistically anchored to a PRC2 dependency, while the speckle call has no retrievable supporting observation at all. Vandenbunder B et al. 2014
  7. E7moderate confidence 3 of 5: One strong study, or several smaller consistent ones.database

    No RING1 localisation result exists in any KMT2A-fusion context. Measured 2026-09-21: (RING1[tiab] OR RING1A[tiab] OR RNF1[tiab]) AND (KMT2A[tiab] OR MLL[tiab] OR "MLL-AF4"[tiab] OR "MLL-AF9"[tiab] OR "MLL-ENL"[tiab] OR "MLL-AF10"[tiab] OR "t(4;11)"[tiab] OR "t(9;11)"[tiab]) AND (localization[tiab] OR localisation[tiab] OR subnuclear[tiab] OR nuclear[tiab] OR nucleolar[tiab] OR speckle[tiab] OR speckles[tiab] OR "PML bodies"[tiab] OR chromatin-bound[tiab] OR cytoplasmic[tiab]) returns 0 records; the unscoped pair (RING1[tiab] OR RING1A[tiab]) AND (KMT2A[tiab] OR MLL[tiab] OR "MLL-AF9"[tiab] OR "MLL-AF4"[tiab]) returns only 3, which is the operand control showing how thin the intersection is to begin with.

    What this evidence cannot show

    Bounded by titles and abstracts only. 'RING1' is also the string this graph must keep apart from RNF2/RING1B and from the PRC1 complex name - data/symbol-collisions.json carries both rows - so this count is over the gene symbol and its aliases, not over the complex, and a PcG-body imaging paper framed at the level of 'PRC1' would be unreachable from it (rule 64). Rule-67 positive control for this query SHAPE: the identical construction, run over all sixteen genes of this tranche on the same day, returned non-zero for seven of them - H2AZ1 1, EED 2, CHAF1B 1, CEBPA 3, TIFAB 1, SAMHD1 1, PROM1 1 - so the instrument can return a one. The querytranslation was read back on every run and confirms the quoted cytogenetic terms expand to "t 4 11"[Title/Abstract] and "t 9 11"[Title/Abstract] and not to a UID filter (rule 95); every term carries its own [tiab] tag rather than sitting inside a parenthesised group (rule 94).

    Evidence that argues against this (1)
    • The complex-level query is the one that can break this absence and it was not run as a counted quantity, which is a real limitation of the bound rather than a rhetorical one: rule 64 exists because gene-ssrp1 recorded a false absence for exactly this reason. Note also that this graph already holds a localisation-polycomb-bodies-kmt2a-r node, so somebody has previously judged the Polycomb-body question relevant to this disease; the zero above means no paper names RING1 and a KMT2A fusion and a compartment in one abstract, not that the compartment is unstudied here. The functional side is well covered - Ring1a/Ring1b double depletion collapses leukaemic identity in Hox-activating fusion leukaemia - so the gap is specifically imaging, in the index disease. Rossi A et al. 2016
Connected to