Oncofusion

start / graph / gene-bag6

Genemoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q78-interactome-absent

BAG6 / BAT3 - a DOT1L partner that is about H3K79me2 itself, reciprocally co-immunoprecipitated, and not a spoke

also called BAT3 · BAG6 · G3 · Scythe · Large proline-rich protein BAG6 · HLA-B-associated transcript 3 · BAG family molecular chaperone regulator 6

BAG6 helps DOT1L put its chemical mark on histone H3 at position 79 - the exact mark that drives KMT2A-rearranged leukaemia. Without BAG6 the mark drops and cells stop repairing radiation damage properly.

The same thing, for a scientist

BAG6/BAT3 (P46379, 1,132 aa) is a proline-rich chaperone-like scaffold with a ubiquitin-like domain, best known for protein quality control and tail-anchored protein targeting. **Its DOT1L connection is the strongest atlas-independent DOT1L partner in this beat's set and it is about the mark this whole project turns on.** In U2OS cells Bat3 co-localises with DOT1L at histone H3; Bat3 knockdown reduces the DOT1L-H3 interaction and **H3K79 dimethylation**, which in turn reduces ionising-radiation-induced 53BP1 foci in G1/G2, causes DNA repair defects and increases radiosensitivity; a conserved Bat3 ubiquitin-like motif and a conserved DOT1L ubiquitin-interacting motif mediate the contact [E2]. IntAct records **two DOT1L-BAG6 rows, both non-spoke, both `MI:0914 association` by anti-bait co-immunoprecipitation, in both directions** [E1]. **This partner is not in the Hein atlas spoke set** that `ana-the-six-new-dot1l-partners-are-nine-spokes-of-one-pulldown` adjudicated - it is a separate, focused, mechanism-first paper, and it had no entry.

Go deeper
Why this is the most consequential of the unwritten DOT1L partners

This graph holds mechanism-dot1l-h3k79-methylation, mechanism-h2bub-dot1l-trans-histone-crosstalk and interface-dot1l-h2bub-ubiquitin - the ubiquitin-dependent arm of DOT1L regulation. Bat3 belongs to that arm and was missing from it: the contact is reported to run through a ubiquitin-like motif on BAG6 and a ubiquitin-interacting motif on DOT1L 2, which is the same chemistry as the H2B-ubiquitin crosstalk this graph already carries, with a protein rather than a nucleosome supplying the ubiquitin-like surface.

That is a mechanistically specific, testable proposition and not an atlas hit: DOT1L's UIM would have two competing ubiquitin-like ligands, H2Bub on the nucleosome and BAG6 in the nucleoplasm. Nobody has put them in the same experiment.

What is not shown, which is most of what this project needs
  • No leukaemia system. U2OS osteosarcoma cells. No KMT2A fusion, no B-lineage, no primary sample (brief rule 73).
  • No fusion arm. Whether BAG6 is required for the H3K79me2 spreading that KMT2A::AFF1 drives is untested, and it is the obvious experiment - a BAG6 knockdown in a KMT2A-rearranged line with an H3K79me2 ChIP over HOXA.
  • Thin corroboration. (DOT1L OR "Dot1L")[tiab] AND (BAG6 OR BAT3)[tiab] returns exactly 1 record on PubMed, the source paper itself 3. Fifteen years, one paper, no replication.
  • BAG6 is a promiscuous chaperone. It is recovered in very many interaction datasets (910 IntAct records), which is the standard argument against reading any single BAG6 co-IP as specific. The counterweight here is that the source ran a functional arm - the mark itself goes down - not just a pull-down.
Facts and figures
uniprotP46379
length AA1132
gene symbolBAG6
protein nameLarge proline-rich protein BAG6 (BAG family molecular chaperone regulator 6, HLA-B-associated transcript 3, Scythe)
uniprot resolutionaccession:P46379, reviewed human, one record; primary gene name read back as BAG6 (entry BAG6_HUMAN), synonyms BAT3, G3; length 1,132 aa checked against UniProt 2026-09-21.
symbol collision checkdata/symbol-collisions.json greped 2026-09-21 for BAG6 and BAT3: no row existed. A row IS proposed in this beat's memo - 'BAT3' is heavily used in the HLA/MHC region literature as a locus name rather than a protein, 'G3' is unusable as a search token, and 'Scythe' is the name most of the apoptosis literature uses, so a BAG6 absence claim built on the current symbol undercounts.
baitDOT1L (Q8TEK3)
total intact records910
shown for fusionNO - nobody has looked in any KMT2A fusion, in any lineage. U2OS osteosarcoma only.
fetched2026-09-21
subnuclear localizationUNPUBLISHED, AND THE BOUND IS AN ABSOLUTE ZERO. (BAG6[tiab] OR BAT3[tiab] OR Scythe[tiab]) AND (nucleolar[tiab] OR "nuclear speckles"[tiab] OR "nuclear bodies"[tiab] OR subnuclear[tiab]) returns ZERO records on 2026-09-21, querytranslation read back and confirmed to carry the Title/Abstract tag on every one of the seven terms. The name list includes both retired/legacy symbols - BAT3, under which most of this protein's literature was published, and Scythe - per this gene's row in data/symbol-collisions.json, which records that a BAG6-only query misses most of the literature. Operand controls: (BAG6 OR BAT3 OR Scythe)[tiab] AND ("nuclear export" OR nucleocytoplasmic OR CRM1 OR "nuclear localization")[tiab] returns 14, so the query shape reaches this protein's compartment literature and the zero is a zero inside a live search. THIS IS A BOUNDED ABSENCE, NOT A NOT APPLICABLE: BAG6 has an annotated NLS at 1012-1054, a documented nuclear pool on four experimental attributions, and a chromatin job, so a subnuclear compartment is a meaningful and unasked question.
localization shown for fusionNO - nobody has localised BAG6 in any KMT2A fusion, in any lineage. This entry's existing data.shown_for_fusion already records 'NO - nobody has looked in any KMT2A fusion, in any lineage. U2OS osteosarcoma only', and the localisation dimension adds nothing to contradict it. The specific unmeasured thing is worth naming: BAG6's nuclear fraction is set by GET4 retention, its nuclear job is to support H3K79me2, and H3K79me2 is the mark KMT2A-fusion leukaemia depends on - so the fusion-context question is not 'where is BAG6' in the abstract but 'what fraction of BAG6 is nuclear in a fusion-bearing blast, and does DOT1L inhibition or menin inhibition change it'.
interaction with dot1l
{
  "source_pmid": "22373577",
  "source_class": "focused mechanistic study - NOT the Hein atlas spoke set",
  "n_intact_records": 2,
  "n_spoke_expanded": 0,
  "n_source_publications": 1,
  "intact_acs": [
    "EBI-7776967",
    "EBI-7776998"
  ],
  "interaction_types": {
    "MI:0914 association": 2
  },
  "detection_methods": [
    "anti bait coimmunoprecipitation"
  ],
  "reciprocal_direction_curated": true,
  "system": "Homo sapiens U2OS osteosarcoma cell",
  "motifs": {
    "BAG6": "conserved ubiquitin-like motif (residues not stated in the abstract)",
    "DOT1L": "conserved ubiquitin-interacting motif (residues not stated in the abstract)"
  },
  "functional_arm": "Bat3 knockdown reduces DOT1L-H3 interaction, H3K79me2, IR-induced 53BP1 foci in G1/G2, and increases radiosensitivity",
  "independent_corroboration": 0,
  "brief_stated_record_count": 1,
  "rest_record_count": 2,
  "shared_pdb_entries": []
}
localization
{
  "subcellular": "CYTOSOL AND NUCLEUS SIMULTANEOUSLY, PLUS A SECRETED POOL - three compartments, all experimentally attributed. UniProt P46379 fetched 2026-09-21 carries 'Cytoplasm, cytosol' on four ECO:0000269 attributions (PubMed:17403783, 20676083, 21636303, 29042515), 'Nucleus' on four (PubMed:14960581, 17403783, 21636303, 29042515) - note that three papers support BOTH - and 'Secreted, extracellular exosome' on two (PubMed:18055229, 18852879). A NUCLEAR LOCALISATION SITE is annotated at residues 1012-1054. The note reads: 'Normally localized in cytosol and nucleus, it can also be released extracellularly, in exosomes, by TUMOR AND MYELOID DENDRITIC CELLS. CYTOPLASMIC RETENTION IS DUE TO INTERACTION WITH GET4.' [E_q89_bag6_loc1]",
  "the_partition_is_regulated_and_the_regulator_is_named": "GET4 holds BAG6 in the cytoplasm. That is a specific, testable, druggable-in-principle mechanism for a nucleocytoplasmic partition, and it matters for this entry because BAG6's relevance here is a NUCLEAR job - facilitating DOT1L-mediated H3K79 dimethylation. If GET4 abundance sets how much BAG6 reaches chromatin, then GET4 is an unexamined upstream regulator of the mark this whole project turns on. Nobody has measured GET4 in a KMT2A-rearranged cell.",
  "subnuclear": "UNPUBLISHED. No subnuclear compartment has been reported for BAG6 in any cell type, and the bounded query returns an absolute zero - see data.subnuclear_localization."
}
cell type
{
  "normal": "IMMATURE DENDRITIC CELLS AT PROTEIN LEVEL is UniProt's only tissue statement, and the exosome route is attributed to TUMOUR AND MYELOID DENDRITIC CELLS [E_q89_bag6_loc1]. That is a myeloid-immune distribution and it is the only cell-type resolution the record offers. A wider bounded query - (BAG6 OR BAT3 OR Scythe)[tiab] AND (\"dendritic cell\" OR exosome OR \"natural killer\")[tiab] - returns 18 records on 2026-09-21, an immunology literature this beat counted and did not enumerate.",
  "where_the_DOT1L_result_was_obtained": "U2OS HUMAN OSTEOSARCOMA CELLS - no haematopoietic system, no KMT2A fusion. This entry already states that plainly and the cell-type field repeats it because the field is what gets machine-read: the single result that makes BAG6 matter to this graph was obtained in a bone tumour line [E_q89_bag6_loc2].",
  "in_this_disease": "NOTHING. This entry's existing E3 bounds the leukaemia literature, and this beat's own control - (BAG6 OR BAT3)[tiab] AND (leukemia OR leukaemia)[tiab] - returns 6 records on 2026-09-21, none of them a KMT2A-fusion study at title level."
}
cell state
{
  "CELL_CYCLE": "The one state with a measurement, and it is in the source paper's own title: Bat3 promotes DNA-damage-induced 53BP1 foci AT G1/G2 CELL-CYCLE PHASES [E_q89_bag6_loc2]. So BAG6's contribution to the damage response is phase-restricted - which dovetails with what this tranche records for TP53BP1, whose nuclear bodies are a G1 structure, and gives the two entries a shared, checkable state.",
  "DAMAGE": "Bat3 knockdown reduces the DOT1L-H3 interaction and H3K79 dimethylation, which in turn reduces ionising-radiation-induced 53BP1 foci, causes DNA repair defects and increases radiosensitivity [E_q89_bag6_loc2].",
  "bounded": "No BAG6 cell-state result in any leukaemic or KMT2A-fusion system."
}
localization bounded absence
{
  "date": "2026-09-21",
  "tool": "NCBI esearch db=pubmed",
  "queries": [
    {
      "query": "(BAG6[tiab] OR BAT3[tiab] OR Scythe[tiab]) AND (nucleolar[tiab] OR \"nuclear speckles\"[tiab] OR \"nuclear bodies\"[tiab] OR subnuclear[tiab])",
      "querytranslation": "(\"BAG6\"[Title/Abstract] OR \"BAT3\"[Title/Abstract] OR \"Scythe\"[Title/Abstract]) AND (\"nucleolar\"[Title/Abstract] OR \"nuclear speckles\"[Title/Abstract] OR \"nuclear bodies\"[Title/Abstract] OR \"subnuclear\"[Title/Abstract])",
      "count": 0,
      "warninglist": "outputmessages: ['No items found.'], quotedphrasesnotfound: [], phrasesignored: []"
    },
    {
      "query": "(BAG6[tiab] OR BAT3[tiab] OR Scythe[tiab]) AND (\"nuclear export\"[tiab] OR nucleocytoplasmic[tiab] OR CRM1[tiab] OR \"nuclear localization\"[tiab])",
      "querytranslation": "(\"BAG6\"[Title/Abstract] OR \"BAT3\"[Title/Abstract] OR \"Scythe\"[Title/Abstract]) AND (\"nuclear export\"[Title/Abstract] OR \"nucleocytoplasmic\"[Title/Abstract] OR \"CRM1\"[Title/Abstract] OR \"nuclear localization\"[Title/Abstract])",
      "count": 14,
      "role": "OPERAND CONTROL - the compartment literature for this protein is reachable by this query shape, so the zero above is not an instrument failure"
    },
    {
      "query": "(BAG6[tiab] OR BAT3[tiab]) AND (leukemia[tiab] OR leukaemia[tiab])",
      "querytranslation": "(\"BAG6\"[Title/Abstract] OR \"BAT3\"[Title/Abstract]) AND (\"leukemia\"[Title/Abstract] OR \"leukaemia\"[Title/Abstract])",
      "count": 6,
      "on_topic_for_kmt2a": 0
    }
  ],
  "name_list_searched": [
    "BAG6",
    "BAT3 (the symbol most of the literature uses)",
    "Scythe"
  ],
  "not_searched": "'G3', UniProt's third synonym - it is two characters and matches essentially anything, which data/symbol-collisions.json already records for this gene.",
  "rule_80_caveat": "All three counts are bounded by TITLES AND ABSTRACTS. A nucleolar or speckle co-stain could sit in a supporting figure of any of the 14 compartment papers and would be invisible here.",
  "absence_class": "never-measured"
}
How this could bite us back
  • BAG6 is a core protein quality-control factor and a tail-anchored protein targeting chaperone. Anything that removes it removes proteostasis in every cell, which makes it a poor target however good the DOT1L link turns out to be.
  • BAG6 is recovered in a very large number of interaction datasets. The reason this one is not dismissed as promiscuous recovery is the functional arm - the mark itself falls - and if that arm fails to replicate, nothing else here survives.
  • The finding would make DOT1L's ubiquitin-interacting motif a shared surface rather than a nucleosome-specific one, which weakens the H2Bub-crosstalk story this graph has written in three entries. That is a cost of accepting it and should be stated rather than absorbed.
Still open
  1. Does BAG6 knockdown reduce H3K79me2 spreading over HOXA in a KMT2A-rearranged line? This is the single most direct test in the beat: an existing knockdown, an existing ChIP, and the mark the disease runs on.
  2. Do H2B-ubiquitin and the BAG6 ubiquitin-like motif compete for DOT1L's ubiquitin-interacting motif? If they do, BAG6 is a nucleoplasmic competitor of the nucleosomal activation signal, which would invert how this graph reads the crosstalk.
  3. Why has one mechanistic paper on H3K79me2 regulation attracted no replication in fifteen years? A BAG6 arm in any published DOT1L dataset would settle whether this is neglected or quietly contradicted.
  4. What fraction of BAG6 is nuclear in a KMT2A-rearranged blast, and does GET4 set it? GET4 is a named cytoplasmic retention factor for a protein that supports H3K79me2 - the mark this disease depends on - and GET4 has never been measured in this disease.
  5. BAG6 supports DOT1L-mediated H3K79me2 in U2OS. Does BAG6 knockdown reduce H3K79me2 in a KMT2A-fusion line, and if so is it an alternative entry point to the same mark that pinometostat targets directly?
  6. BAG6's damage function is restricted to G1/G2 and TP53BP1's nuclear bodies are a G1 structure. Are the two observations the same phenomenon seen from two sides, and does BAG6 knockdown change 53BP1 nuclear-body number as distinct from IRIF number?
Every source behind this entry (5)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    IntAct's REST record holds two DOT1L-BAG6 rows, EBI-7776967 and EBI-7776998, both typed MI:0914 association by anti-bait co-immunoprecipitation in human U2OS cells, neither spoke-expanded, curated in both directions, both from PMID 22373577; BAG6 carries 910 IntAct records in total, of which these two are the only ones against a core bait.

    What this evidence cannot show

    One database on one day, REST endpoint (brief rule 93). Two records from ONE publication, curated in both directions - an internal control, not independent replication. BAG6's 910 total records make it a high-degree node in IntAct generally, which raises the prior on non-specific recovery in any single dataset.

    Evidence that argues against this (2)
    • 'Curated in both directions' is one figure curated twice, not two experiments. Re-read at the endpoint on 2026-09-21, EBI-7776967 and EBI-7776998 both carry the single annotation 'figure legend (f4a)' and both carry intactMiscore 0.35; they differ only in which accession holds the bait role. So the reciprocity here is a curation convention applied to one panel, not the reciprocal-co-IP control that phrase normally signals. For comparison, the PSIP1-SUMO1 rows in this same beat are annotated to three different figures (f1d, f1e, f5a/f5b) and the PSIP1-RBBP8 rows score 0.6. EMBL-EBI IntAct 2026
    • The 910 that carries the promiscuity argument is itself an endpoint number, and BAG6 is one of the accessions where the endpoints diverge most. Measured the same day, PSICQUIC id:P46379 returns 311 against REST's 910 - so under the query form this project's two earlier interactome analyses used, BAG6 is a third as high-degree and the prior on non-specific recovery that this caveat rests on is a third as strong. A promiscuity argument built on a raw record count inherits whatever the endpoint happens to expose. EMBL-EBI IntAct and PSICQUIC 2026
  2. E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    In human U2OS osteosarcoma cells (no haematopoietic system, no KMT2A fusion), Bat3 co-localises with DOT1L at histone H3 and Bat3 knockdown reduces the DOT1L-H3 interaction and H3K79 dimethylation, reducing ionising-radiation-induced 53BP1 foci in G1/G2 phases, causing DNA repair defects and increasing radiosensitivity; a conserved Bat3 ubiquitin-like motif and a conserved DOT1L ubiquitin-interacting motif promote the Bat3-DOT1L interaction.

    What this evidence cannot show

    Abstract read this session; full text not retrieved. U2OS osteosarcoma - no haematopoietic system, no KMT2A fusion, no primary sample (brief rule 73). The mechanism rests on knockdown rather than on a separation-of-function mutant of the motifs, and residue boundaries for the UBL and UIM are not in the abstract, so none are asserted here. New to this graph (checked with scripts/check-citation-reuse.py).

    Evidence that argues against this (1)
    • The paper's own framing is that H3K79me2 is negligible during S phase and matters for 53BP1 only in G1/G2 when H4K20me2 is low, because 53BP1 binds H4K20me2 with much higher affinity. So the H3K79me2 arm of 53BP1 recruitment is conditional on cell-cycle phase, and a BAG6 effect measured outside G1/G2 would be expected to show nothing. Wakeman TP et al. 2012
  3. E3moderate confidence 3 of 5: One strong study, or several smaller consistent ones.database

    As of 2026-09-21, PubMed returns exactly 1 record for (DOT1L OR 'Dot1L')[tiab] AND (BAG6 OR BAT3)[tiab] - the source paper itself - and 8 for (BAG6 OR BAT3)[tiab] AND (MLL OR KMT2A OR leukemia)[tiab], none of which concerns DOT1L.

    What this evidence cannot show

    Titles and abstracts only; supporting figures not searched (brief rule 80). Name list tried: DOT1L, Dot1L, BAG6, BAT3. The aliases Scythe, G3 and the phrase 'HLA-B-associated transcript 3' were NOT run - and Scythe in particular is the name much of the apoptosis literature uses, so this count is a floor. Operand control (brief rule 67): each clause alone returns a large literature, so the one is a real intersection.

    Evidence that argues against this (2)
    • The alias gap this caveat calls a floor was measured and is not one, and the field tag is not doing what the caveat says. Re-run 2026-09-21: adding Scythe, BAG-6 and "HLA-B-associated transcript 3" to the name list leaves both counts exactly where they were - 1 and 8 - while Scythe[tiab] alone returns 65, so the instrument reaches the apoptosis literature and the intersection with DOT1L is genuinely empty beyond the source paper. Separately, PubMed's querytranslation shows that the [tiab] after each parenthesised OR group is DROPPED and both clauses expand to [All Fields], so these are all-fields counts and not the title-and-abstract counts the caveat describes - which makes the 1 a stronger absence than claimed, not a weaker one. NCBI PubMed 2026
    • The query's frame, not its name list, is what hides the relevant corroboration. Bounding on 'DOT1L or leukaemia' cannot reach BAG6's independent nuclear chromatin biology: Bach et al. 2015 identify BAT3 (Scythe/BAG6) as a nuclear partner of the transcriptional repressor TRPS1 in oestrogen-receptor-positive breast cancer cells, show BAG6 silencing blocks nuclear accumulation of cathepsin D, and place both proteins on chromatin. So 'one paper, no replication in fifteen years' is true of the DOT1L pair and false of the premise behind it - that BAG6 has no business on chromatin - and this entry's promiscuous-chaperone objection is correspondingly weaker than it looks. Bach AS et al. 2015
  4. E_q89_bag6_loc1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    UniProt P46379 (BAG6_HUMAN, primary gene BAG6, synonyms BAT3 and G3, 1,132 aa, read back 2026-09-21) carries THREE subcellular locations, all experimentally attributed: 'Cytoplasm, cytosol' (four ECO:0000269), 'Nucleus' (four ECO:0000269, three of them shared with the cytosolic call) and 'Secreted, extracellular exosome' (two ECO:0000269). A NUCLEAR LOCALISATION SITE is annotated at residues 1012-1054. The note states that BAG6 is 'normally localized in cytosol and nucleus', can be released extracellularly in exosomes by TUMOR AND MYELOID DENDRITIC CELLS, and that 'CYTOPLASMIC RETENTION IS DUE TO INTERACTION WITH GET4'. Tissue specificity: 'Expressed by immature dendritic cells (at protein level)'.

    What this evidence cannot show

    Statement about the record. Unlike BICRA, CTCF, PARP1 and PRDM9 in this tranche, BAG6's compartment annotations are numerous and experimentally coded and this beat did NOT open them to check rule 91 - so the attributions are reported as the database gives them and have not been verified as being about localisation. The tissue comment names one cell type at protein level and is uncoded.

    Evidence that argues against this (1)
    • Three simultaneous compartments invite a reading this entry should resist: that BAG6 is 'everywhere' and therefore its compartment carries no information. The opposite is closer to true, and the GET4 clause is why. A protein partitioned between cytosol and nucleus BY A NAMED RETENTION FACTOR has a compartment that is a variable, not a constant, and the variable has a handle on it. The honest gap is different and larger: nobody has measured the nuclear FRACTION in any cell, so 'cytosol and nucleus' could describe 99:1 or 1:1, and the entire relevance of BAG6 to this graph - supporting DOT1L's H3K79 dimethylation - depends on the nuclear pool being non-trivial in a haematopoietic cell. The U2OS knockdown result shows the nuclear pool is functionally significant THERE; that is one cell type, and a bone tumour line. Wakeman TP et al. 2012
  5. E_q89_bag6_loc2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    BAG6's ONE FUNCTIONALLY DECISIVE RESULT IS NUCLEAR, IS CELL-CYCLE-PHASE-RESTRICTED, AND IS IN A BONE TUMOUR LINE. In human U2OS osteosarcoma cells - no haematopoietic system, no KMT2A fusion - Bat3 co-localises with DOT1L at histone H3; Bat3 knockdown reduces the DOT1L-H3 interaction and H3K79 DIMETHYLATION, which in turn reduces ionising-radiation-induced 53BP1 foci AT G1/G2 CELL-CYCLE PHASES, causes DNA repair defects and increases radiosensitivity; a conserved Bat3 ubiquitin-like motif and a conserved DOT1L ubiquitin-interacting motif mediate the contact.

    What this evidence cannot show

    This restates this entry's existing E2 with the localisation content foregrounded and the identifiers re-fetched rather than copied from the sibling block. U2OS osteosarcoma only. The 'co-localises with DOT1L at histone H3' phrasing is the source's; it is a biochemical co-association statement rather than a subnuclear compartment assignment, and this entry does not upgrade it into one. Abstract-level reading.

    Evidence that argues against this (1)
    • The most useful objection is to this beat's own framing rather than to the paper. Calling 'co-localises with DOT1L at histone H3' a localisation result would be a category error of exactly the kind this tranche found in BICRA and MAML2: it is co-association with a chromatin substrate, which constrains the compartment to 'nuclear, on chromatin' - something the NLS at 1012-1054 and four ECO:0000269 nuclear attributions already establish - and adds no subnuclear address at all. That is why this entry's subnuclear field records an absolute zero rather than borrowing the DOT1L association. The separate and real limitation is the system: H3K79me2 is the mark KMT2A-fusion leukaemia lives on, the only paper connecting BAG6 to it used an osteosarcoma line, and nothing guarantees the GET4-set nuclear partition is the same in a blast. UniProt Consortium 2026
Connected to