Oncofusion

start / graph / gene-sfpq

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

SFPQ / PSF (P23246) - the last of 21 fusion-construct partners without an entry, and it is itself the 5' half of an ALL fusion that puts ABL1 in the nucleus

also called SFPQ · PSF · Splicing factor, proline- and glutamine-rich · polypyrimidine tract-binding protein-associated splicing factor · SFPQ_HUMAN · P23246 · SFPQ-ABL1 · SFPQ::ABL1

SFPQ is a nuclear RNA-handling protein that turned up stuck to a laboratory-made MLL fusion protein, and it was the last of twenty-one such partners this project had never written down. Separately and more strikingly, SFPQ is itself the front half of a different leukaemia-causing fusion, and that fusion drags a well-known cancer enzyme into the nucleus, where it drives the disease by a measurably different route.

The same thing, for a scientist

SFPQ (P23246, SFPQ_HUMAN, 707 aa, 76,149 Da) is a DBHS-family RNA-binding protein with two RRMs (297-369, 371-452) flanked by long disordered regions (1-273, 579-707) and an N-terminal RGG stretch (9-27); UniProt places it in the **nucleus speckle**, **nucleus matrix** ("predominantly in nuclear matrix") and cytoplasm. It entered this graph as an absence: the cycle-55 loud-skip fix on `core-complex-interactome-gap` surfaced a fifth IntAct fusion construct, `human_mll_gas7_fusion_protein` (EBI-1157918), and SFPQ was **the only one of 21 fusion-construct partners with no entry** - its two co-partners on the same construct and the same paper, KHDRBS1 and PRMT1, both had one. The row is anti-tag co-IP in HEK293, human, type `association`, from **PMID 26766589** (Cheung, *Cancer Cell* 2016), a paper this graph already cites ten times and whose abstract **never names SFPQ**. **The reason the entry is worth more than closing a gap is SFPQ::ABL1.** SFPQ is the 5' partner of a recurrent ABL-class fusion in B-cell precursor ALL - **SFPQ exon 9 to ABL1 exon 4 in all reported cases**, only six such cases reported as of 2021, typically adolescents/young adults, recurrent IKZF1 deletions (PMID 32306475). Because the break is in ABL1 intron 4, the chimaera **lacks the ABL1 SH2 domain** (PMID 21435002). And functionally it is not BCR-ABL1 with a different hat: SFPQ-ABL1 transforms cytokine-dependent lines and is TKI-sensitive, but **localises to the nuclear compartment**, is a **weaker** proliferative driver, **fails to activate PI3K/AKT**, down-regulates ErbB/NF-kB/VEGF/MAPK while up-regulating cell-cycle, DNA-replication and **spliceosome** phosphosignalling, and depends on Mcl-1/Bcl-xL (navitoclax, S-63845 sensitive) - PMID 35061886, whose own closing sentence is that these findings "highlight the role that fusion partners have in mediating the function of ABL1 fusions". That is this project's central thesis measured on a different oncoprotein: **same catalytic domain, different 5' partner, different subcellular address and a different signalling network.**

What it looks like
Splicing factor, proline- and glutamine-rich707 aa
RGG repeats (3 x 3-aa R-G-G) · residues 9–27 · UniProt REGION. Inside the long N-terminal disordered stretch.Disordered (N-terminal)Disordered (N-terminal) · residues 1–273 · UniProt REGION. Contains the RGG repeats and the proline/glutamine-rich low-complexity sequence the protein is named for.RRM 1RRM 1 · residues 297–369 · UniProt DOMAIN.RRM 2RRM 2 · residues 371–452 · UniProt DOMAIN. Immediately abuts RRM 1.Disordered (C-terminal)Disordered (C-terminal) · residues 579–707 · UniProt REGION.0200400600

No three-dimensional model is available for this protein, so the map above is the whole picture. That is itself informative: AlphaFold does not model chains this long, and the parts that have been crystallised are held under the entries for the individual domains.

Go deeper
Why this entry exists: the last gap of twenty-one

analyses/core-complex-interactome-gap/run.py silently dropped every IntAct record whose participant is a fusion CONSTRUCT, because such an interactor carries no cross-references and the script's gene_of() regex finds no (gene name) to parse. Cycle 55 made the skip loud. The report surfaced a fifth construct, human_mll_gas7_fusion_protein (EBI-1157918), taking the enumeration to 50 rows and 21 distinct partners - 20 of which already had an entry.

SFPQ was the one that did not, which made it the cheapest identifiable interactome gap in the project 2. Two facts make the omission worse rather than better:

  • Its co-partners on the same construct, same paper, same experiment - KHDRBS1 (Q07666) and PRMT1 (Q99873) - both have entries. The experiment was read; one row of it was not.
  • The source, PMID 26766589, is cited ten times in this graph, including in gene-prmt1 and gene-kdm4c. The biology was known. The fusion-side row was invisible.

So this is not an absence of literature. It is an absence created by an instrument, in a paper the project had already mined.

What SFPQ is, read from UniProt today

P23246, SFPQ_HUMAN, Homo sapiens, 707 aa, 76,149 Da, gene SFPQ, synonym PSF 1.

featurecoordinates
RRM 1297-369
RRM 2371-452
Disordered1-273
Disordered579-707
3 x 3-aa R-G-G repeats9-27

Subcellular location, verbatim from the record: Nucleus speckle, Nucleus matrix, Cytoplasm, with the note "Predominantly in nuclear matrix".

Read that carefully, because the compartment names collide. UniProt says nuclear speckle; this graph's localization-paraspeckles-neat1-kmt2a-r lists SFPQ among the paraspeckle marker proteins (NEAT1, NONO, SFPQ, PSPC1), and nuclear speckles and paraspeckles are different bodies. Both are defensible: SFPQ is a DBHS protein and a verified component of the HEXIM1-NEAT1 HDP-RNP alongside NONO, PSPC1, RBM14 and MATRIN3 5. But an entry that wrote "SFPQ is a paraspeckle protein" on UniProt's authority would be citing a record that says speckle. The two names are recorded separately here for that reason.

Two structural gaps, stated rather than filled. The fields fetched were accession, names, length, mass, subcellular location, domains and regions; they return no coiled-coil and no NOPS/DBHS dimerisation domain annotation. That matters for the oligomerisation question below, and nothing here should be read as evidence that SFPQ lacks such a region - only that this fetch did not ask for, and did not return, one.

SFPQ::ABL1 - the same kinase, a different compartment, a different network

This is the part of SFPQ that matters to a fusion-oncoprotein knowledge graph, and it is not the co-IP row.

The lesion. A recurrent but rare ABL-class fusion of B-cell precursor ALL. A FISH screen of 55 paediatric and 50 adult "B-other" cases found ABL-class aberrations in 3 (6%) of adults and 0 of children, with RT-PCR confirming SFPQ-ABL1 in one adult carrying t(1;9)(p34;q34). Reviewing every reported case, only six SFPQ-ABL1-positive BCP ALLs existed as of that paper, all with the identical junction - SFPQ exon 9 to ABL1 exon 4 - typically in adolescents/younger adults without hyperleukocytosis, with recurrent IKZF1 deletions; the few patients given neither TKI nor allogeneic transplant relapsed 3.

The structural consequence of that junction. Breaks in ABL1 intron 4 - SFPQ-ABL1 and RCSD1-ABL1 - yield chimaeras that lack the ABL1 SH2 domain, and both are associated with B-cell ALL. The same review states the general rule for ABL1 fusions: the kinase domain is always retained, and the N-terminal partner often contributes a coiled-coil or helix-loop-helix domain whose oligomerisation is required for kinase activation, cytoskeletal localisation and transformation 4.

The functional consequence, which is the striking part. SFPQ-ABL1 expressed in cytokine-dependent lines was sufficient to transform them and remained TKI-sensitive - so the kinase works. But set against BCR-ABL1 in the same study [E3b]:

BCR-ABL1SFPQ-ABL1
compartment(comparator)nuclear
proliferative drive(comparator)weaker
PI3K/AKTactivatednot activated
up in phosphoproteome-cell cycle, DNA replication, spliceosome
down in phosphoproteome-ErbB, NF-kB, VEGF, MAPK
cell-cycle phosphorylation-G2/M proteins
survival dependency-Mcl-1 / Bcl-xL; navitoclax- and S-63845-sensitive

Why this belongs in this graph. The project's organising claim is that the 5' partner is not a delivery vehicle for a catalytic domain - it sets localisation, complex membership and therefore what the oncoprotein does. Here that claim is tested on a kinase fusion rather than a chromatin fusion, by direct comparison of two fusions sharing the same kinase, and the partner changes the subcellular address, the proliferative rate, the pathway set and the drug dependency. The authors' own conclusion is the thesis in one line: these findings "highlight the role that fusion partners have in mediating the function of ABL1 fusions."

Note the direction of the analogy and its limit: SFPQ-ABL1 goes into the nucleus, whereas mechanism-calm-af10-crm1-nuclear-export-requirement in this graph concerns a fusion whose transforming activity requires nuclear export. Both are partner-set addresses; neither predicts the other.

What the MLL-GAS7 row does and does not support

The row, in full: SFPQ P23246 (uniprotkb), taxid 9606, against human_mll_gas7_fusion_protein EBI-1157918, detection anti tag coip, interaction type association, host Homo sapiens HEK293 embryonic kidney cell, publication 26766589 (pubmed) / EBI-11512485 (intact) 2.

Four limits, each of which matters:

  1. The type is association, not physical association. The PAX5 fusion-construct rows in the same enumeration are typed physical association; this one is the weaker term. Do not upgrade it in citation.
  2. HEK293 is not a leukaemia cell and not a B-cell precursor. This is a transfected tagged construct in embryonic kidney cells, so the row is evidence about the construct, not the patient lesion - the objection this graph applies to the Skucha AP-MS network, and with more force, since that network at least used leukaemia lines with a negative control.
  3. The construct is MLL-GAS7, not KMT2A::AFF1. GAS7 is a non-elongation, cytoskeletal-class partner; the index fusion is not in this row.
  4. PMID 26766589's abstract never names SFPQ. The interaction is curator-extracted from the paper's data, so the association's experimental context - which figure, what controls, whether it replicated - has not been read here [E2 caveats].

What it is nonetheless. It is the first physical link in this graph between a paraspeckle/DBHS protein and any KMT2A fusion. That is worth recording precisely because the paraspeckle beat is otherwise empty - and it is emphatically not a refutation of it; see below.

The paraspeckle near-miss, and why it does not refute the paraspeckle entry

localization-paraspeckles-neat1-kmt2a-r records that direct evidence for paraspeckles or NEAT1 in KMT2A-rearranged leukaemia is none, after a dedicated search, and lists SFPQ among the compartment's marker proteins. SFPQ is independently verified as a component of the HEXIM1-NEAT1 HDP-RNP with DNA-PKcs, Ku70, Ku80, NONO, PSPC1, RBM14 and MATRIN3, assembly requiring HEXIM1 binding to NEAT1 5 - and gene-hexim1 already holds that.

So a paraspeckle protein is now curated as associating with an MLL fusion construct. This does not change that entry's finding, and it would be an error to say it does. A co-IP with a transfected MLL-GAS7 construct in HEK293 says nothing about whether a paraspeckle exists, is altered, or matters in a KMT2A-rearranged leukaemic cell; the compartment was never assayed. Recording it as a refutation would convert an absence of measurement into a measurement, which is the failure mode this graph's absence-bounding discipline exists to prevent.

What it is: a queued experiment's rationale, and a reason the paraspeckle absence is worth a measurement rather than a shrug.

Facts and figures
uniprotP23246
uniprot entry nameSFPQ_HUMAN
gene symbolSFPQ
synonymPSF
protein nameSplicing factor, proline- and glutamine-rich
length AA707
mass da76149
organismHomo sapiens
not annotated in the fields fetchedNo coiled-coil and no NOPS/DBHS dimerisation domain were returned. The fetch requested accession, names, length, mass, subcellular location, ft_domain and ft_region only, so this is a gap in the QUERY and not a claim about the protein.
localizationUniProt: Nucleus speckle; Nucleus matrix; Cytoplasm. Note: 'Predominantly in nuclear matrix'.
subnuclearTwo distinct assignments that must not be merged. (1) UniProt controlled vocabulary: NUCLEAR SPECKLE and NUCLEAR MATRIX. (2) Literature/DBHS: PARASPECKLE protein, verified as a component of the HEXIM1-NEAT1 HDP-RNP with NONO, PSPC1, RBM14 and MATRIN3 (PMID 28712728). Nuclear speckles and paraspeckles are different bodies; this graph's localization-paraspeckles-neat1-kmt2a-r lists SFPQ as a paraspeckle marker, UniProt does not.
cell type evidence exists inHEK293 embryonic kidney (the MLL-GAS7 co-IP row, PMID 26766589); cytokine-dependent cell lines, ectopic expression (SFPQ-ABL1 vs BCR-ABL1, PMID 35061886); B-cell precursor ALL patient cases, adolescents/younger adults (PMID 32306475). NO evidence in this graph places SFPQ in a KMT2A-rearranged leukaemic cell, an infant B-ALL blast, or any pro-B cell.
cell stateNot measured for SFPQ in any state relevant to this project - no quiescence, differentiation-stage or treatment-state data. The SFPQ-ABL1 phosphoproteome reports G2/M cell-cycle protein phosphorylation and up-regulated cell-cycle and DNA-replication signalling relative to BCR-ABL1, which is a statement about the FUSION in ectopic expression, not about wild-type SFPQ.
epigeneticsSFPQ is not a chromatin writer, reader or eraser and no histone mark is associated with it here. The one connection is indirect and belongs to the source paper rather than to SFPQ: PMID 26766589 is an epigenetic-network paper (PRMT1, an H4R3 methyltransferase, and the H3K9 demethylase KDM4C), and SFPQ appears in its fusion-construct co-IP rows alongside PRMT1.
why this entry existsSFPQ was the only one of 21 IntAct fusion-construct partners with no entry in this graph, identified by the cycle-55 loud-skip fix on analyses/core-complex-interactome-gap/run.py. Closing it was the cheapest identifiable interactome gap in the project.
shown for fusionfalse
domains noteCoordinates are UniProt P23246 DOMAIN and REGION features, fetched 2026-09-22. No coiled-coil and no NOPS/DBHS dimerisation feature was returned by the fields requested, so none is listed; that is a gap in the query, not a claim about the protein. No fate is annotated because SFPQ is not a KMT2A fusion partner -- in SFPQ::ABL1 it is the 5-prime partner and the junction is SFPQ exon 9, which this entry does not resolve to a residue.
absence class noteRECLASSIFIED 2026-09-23 (cycle 76). This field held free text, which `scripts/check-absence-class.py` rejects; the prose is preserved here VERBATIM and unsummarised because it is more informative than the token that replaced it. Token chosen: NONE, field removed - 'not-applicable' was honest and there is no vocabulary token for it, because THERE IS NO ABSENCE LEFT: this entry closed the last of the 21 fusion-construct partner gaps. A token here would assert a gap that the entry itself eliminated, so the field is removed rather than filled. An entry with no absence should carry no absence_class. ORIGINAL absence_class, verbatim: «not-applicable»
domains
Disordered (N-terminal)1.000Disordered (N-terminal): 1RGG repeats (3 x 3-aa R-G…9.000RGG repeats (3 x 3-aa R-G-G): 9RRM 1297.0RRM 1: 297RRM 2371.0RRM 2: 371Disordered (C-terminal)579.0Disordered (C-terminal): 579
domains — the numbers behind the chart
[
  {
    "name": "RGG repeats (3 x 3-aa R-G-G)",
    "start": 9,
    "end": 27,
    "note": "UniProt REGION. Inside the long N-terminal disordered stretch."
  },
  {
    "name": "Disordered (N-terminal)",
    "start": 1,
    "end": 273,
    "note": "UniProt REGION. Contains the RGG repeats and the proline/glutamine-rich low-complexity sequence the protein is named for."
  },
  {
    "name": "RRM 1",
    "start": 297,
    "end": 369,
    "note": "UniProt DOMAIN."
  },
  {
    "name": "RRM 2",
    "start": 371,
    "end": 452,
    "note": "UniProt DOMAIN. Immediately abuts RRM 1."
  },
  {
    "name": "Disordered (C-terminal)",
    "start": 579,
    "end": 707,
    "note": "UniProt REGION."
  }
]
fusion construct row
{
  "construct": "human_mll_gas7_fusion_protein (EBI-1157918)",
  "partner_id": "P23246 (uniprotkb)",
  "taxid": 9606,
  "detection": "anti tag coip",
  "interaction_type": "association (NOT 'physical association' - the weaker of the two terms in this enumeration)",
  "host": "Homo sapiens HEK293 embryonic kidney cell",
  "publication": "26766589 (pubmed); EBI-11512485 (intact)",
  "co_partners_same_construct_same_paper": "KHDRBS1 (Q07666), PRMT1 (Q99873) - both already had entries",
  "source": "analyses/intact-fusion-construct-interactors/results.json, run 2026-09-22"
}
sfpq abl1
{
  "junction": "SFPQ exon 9 to ABL1 exon 4 in all reported cases (PMID 32306475)",
  "structural_consequence": "break in ABL1 intron 4, so the chimaera lacks the ABL1 SH2 domain (PMID 21435002)",
  "karyotype_in_the_confirmed_case": "t(1;9)(p34;q34)",
  "disease": "B-cell precursor ALL, Ph-like / ABL-class; adolescents and younger adults, typically without hyperleukocytosis",
  "reported_cases_as_of_2021": 6,
  "screen_denominator": "55 paediatric + 50 adult B-other cases; ABL-class aberrations in 3 (6%) adult, 0 paediatric; SFPQ-ABL1 in 1 of 105",
  "recurrent_cooperating_lesion": "IKZF1 deletions",
  "localization_vs_bcr_abl1": "NUCLEAR compartment, in contrast to BCR-ABL1 (PMID 35061886)",
  "proliferation_vs_bcr_abl1": "weaker driver",
  "pathways_up": "cell cycle, DNA replication, spliceosome",
  "pathways_down": "ErbB, NF-kB, VEGF, MAPK; PI3K/AKT not activated",
  "apoptotic_dependency": "Mcl-1 and Bcl-xL maintained; sensitive to navitoclax and S-63845",
  "therapeutic": "TKI-sensitive; retrospective review found relapse in the few patients given neither TKI nor allogeneic transplant"
}
How this could bite us back
  • Nothing here supports giving any drug to anyone. The TKI, navitoclax and S-63845 sensitivities in E3b were measured in cytokine-dependent cell lines ectopically expressing a fusion, and the relapse observation in E3 is a retrospective note on a handful of patients in a case review, not a trial result. SFPQ-ABL1 is also a different disease from this project's index lesion: it is a BCP-ALL kinase fusion, not a KMT2A rearrangement, and no therapeutic inference should cross between them.
  • The most citable sentence in this entry - that the 5' partner changes the address and the network of the same kinase - is drawn from one paper's abstract comparing two ectopically expressed constructs. It is a good result and it is not a law. Note in particular that BOTH fusions stayed TKI-sensitive, so the partner did not change the actionable target, and that a rival explanation exists in which the chimaera's missing ABL1 SH2 domain does the work instead of the partner.
  • This entry must not be cited as evidence that paraspeckles matter in KMT2A-rearranged leukaemia. `localization-paraspeckles-neat1-kmt2a-r` records zero direct evidence after a dedicated search, and an anti-tag co-IP in HEK293 against an MLL-GAS7 construct does not assay a paraspeckle. The compartment remains unmeasured in this disease.
  • The MLL-GAS7 row is typed `association`, not `physical association`, comes from a paper whose abstract never names SFPQ, and has no reported negative control. It is the weakest evidence item in this entry and the entry's opening sentence should not be allowed to borrow confidence from the SFPQ-ABL1 material, which is independent of it.
Still open
  1. What does the SFPQ moiety contribute to SFPQ-ABL1? The general rule for ABL1 fusions is that the 5' partner supplies a coiled-coil or HLH domain whose oligomerisation is required for kinase activation (PMID 21435002), but that is stated as 'often' and the UniProt fields fetched here return no such domain for SFPQ - only two RRMs, long disordered regions and an RGG stretch. A targeted query for coiled-coil, NOPS and DBHS annotations in P23246, plus the SFPQ exon 9 boundary in residue coordinates, would settle what is actually in the chimaera.
  2. Does the ABL1 SH2 deletion, rather than the SFPQ moiety, explain the altered phosphoproteome and weaker proliferation of SFPQ-ABL1? The two explanations are confounded in every experiment cited here, and an SH2-deleted BCR-ABL1 comparator would separate them. This is the same confound structure as the polarity-versus-MBM pair already in this graph.
  3. Which figure of PMID 26766589 contains the SFPQ / MLL-GAS7 co-IP, and with what controls? The abstract never names SFPQ, so the row is curator-extracted, and the graph cites this paper ten times without anyone having read its interaction data. The full text would also show whether KHDRBS1, PRMT1 and SFPQ were recovered in one experiment or three.
  4. Is SFPQ curated against any other KMT2A fusion construct, or against KMT2A itself? It appears here only against MLL-GAS7, a cytoskeletal-class partner, and a single construct row is the weakest form this enumeration produces.
  5. Has SFPQ ever been measured in a KMT2A-rearranged cell at all - expression, localisation or dependency? This entry records evidence from HEK293, from ectopic expression in cytokine-dependent lines, and from BCP-ALL patient cases, and NONE of it is in a KMT2A-rearranged context. DepMap would answer the dependency half cheaply.
  6. Does the nuclear localisation of SFPQ-ABL1 involve a paraspeckle or any named body? PMID 35061886 says only 'nuclear compartment'. Given that the SFPQ moiety carries the protein's paraspeckle associations, this is the obvious question and the abstract does not touch it.
Every source behind this entry (6)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    SFPQ is UniProt P23246 (SFPQ_HUMAN), Homo sapiens, 'Splicing factor, proline- and glutamine-rich', gene SFPQ, synonym PSF, 707 aa, 76,149 Da. Annotated features: RRM 1 at 297-369, RRM 2 at 371-452, disordered regions 1-273 and 579-707, and three 3-aa R-G-G repeats at 9-27. Subcellular location: Nucleus speckle, Nucleus matrix, Cytoplasm, with the note 'Predominantly in nuclear matrix'.

    What this evidence cannot show

    Length, mass, accession, entry name and every coordinate quoted here were read from the JSON response on 2026-09-22, not from recall. The fetch requested only the fields listed, so absence of a coiled-coil or NOPS/DBHS dimerisation annotation in this evidence item is an absence in the QUERY, not in the record - no claim is made that SFPQ lacks such a region. UniProt subcellular assignments are a controlled vocabulary and 'Nucleus speckle' is NOT 'paraspeckle'; the paraspeckle assignment used elsewhere in this graph rests on the DBHS literature and on PMID 28712728, not on this record.

    Evidence that argues against this (1)
    • A UniProt localisation set is a union over experiments, cell types and methods, not a statement about any one cell. 'Nucleus speckle, Nucleus matrix, Cytoplasm' with 'predominantly nuclear matrix' does not tell you where SFPQ is in a B-cell precursor, in a leukaemic blast, or in a cell expressing a KMT2A fusion, and this graph has no imaging of SFPQ in any such cell.
  2. E2weak confidence 2 of 5: Preliminary, small, indirect, or not yet peer reviewed.paper

    IntAct curates SFPQ (P23246, taxid 9606) as an `association` with the fusion construct `human_mll_gas7_fusion_protein` (EBI-1157918), detected by anti-tag co-immunoprecipitation in Homo sapiens HEK293 embryonic kidney cells, from PMID 26766589 (IntAct publication EBI-11512485). In the cycle-55 enumeration of 50 fusion-construct interaction rows spanning five constructs and 21 distinct partners, SFPQ was the only partner with no entry in this graph; its two co-partners on the same construct and the same publication, KHDRBS1 (Q07666) and PRMT1 (Q99873), both had one.

    Targeting Aberrant Epigenetic Networks Mediated by PRMT1 and KDM4C in Acute Myeloid Leukemia. · Cheung N, Fung TK, Zeisig BB, Holmes KB, Rane JK, et al. · Cancer Cell 2016
    What this evidence cannot show

    PMID 26766589's title, journal, year, DOI and first author were verified live by efetch on 2026-09-22, and the abstract text was checked: it NEVER NAMES SFPQ. The interaction is therefore curator-extracted from the paper's figures or supplement, and the experimental context - which figure, which controls, whether it replicated, what the stoichiometry was - has NOT been read here; the full text was not obtained. The IntAct interaction type is `association`, the weaker of the two terms used across these rows, and no negative control is reported in the row. The system is a transfected tagged construct in HEK293 embryonic kidney cells: neither a leukaemia cell nor a B-cell precursor. The construct is MLL-GAS7, NOT the index fusion KMT2A::AFF1. The 50-row / 21-partner denominator inherits its own FLOOR caveat - the construct list was assembled by hand, so further fusion-construct interactors may exist.

    Evidence that argues against this (2)
    • The natural reading - that a paraspeckle protein binds an MLL fusion, so paraspeckles are implicated in KMT2A-rearranged leukaemia - is not supported and is contradicted by what was actually measured. `localization-paraspeckles-neat1-kmt2a-r` records ZERO direct evidence for NEAT1 or paraspeckles in a KMT2A-rearranged context after a dedicated search, and a co-IP in HEK293 against an MLL-GAS7 construct does not assay a paraspeckle at all. This row raises the value of doing that measurement; it does not substitute for it.
    • That SFPQ was the single uncovered partner of 21 is partly an artefact of the coverage rule, which tests whether a `gene-<symbol>` or `protein-<symbol>` file EXISTS rather than whether it says anything. Twenty of twenty-one being 'covered' is a statement about file names, and several of those entries may mention the protein only in passing. The gap this entry closes was real; the 20/21 that flattered the instrument should not be over-read.
  3. E3moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    SFPQ is itself the 5' partner of a recurrent ABL-class fusion in B-cell precursor ALL. FISH screening of 55 paediatric and 50 adult 'B-other' BCP-ALL cases found ABL-class aberrations (ABL1, ABL2, CSF1R, PDGFRB) in 3 (6%) of the adult and none of the childhood cases; RT-PCR and sequencing confirmed SFPQ-ABL1 in one adult case with t(1;9)(p34;q34). Reviewing all reported cases including that one, only six SFPQ-ABL1-positive BCP ALLs had been described, ALL of them harbouring a fusion between exon 9 of SFPQ and exon 4 of ABL1; the fusion is typically found in adolescents or younger adults without hyperleukocytosis, IKZF1 deletions are recurrent, and the few patients treated with neither a tyrosine kinase inhibitor nor allogeneic stem cell transplantation relapsed.

    SFPQ-ABL1-positive B-cell precursor acute lymphoblastic leukemias. · Biloglav A, et al. · Genes, Chromosomes & Cancer 2021
    What this evidence cannot show

    Abstract-level only; the full text and the case-by-case review table were not read. Every number here is quoted from the abstract as fetched by efetch on 2026-09-22 - 55 paediatric, 50 adult, 3 (6%) adult, 0 childhood, six cases total, SFPQ exon 9 to ABL1 exon 4. 'Six reported cases' is a 2021 literature count and will have moved; it is not a current incidence. The 6% figure is ABL-class aberrations of any kind in ADULT B-other cases, NOT the frequency of SFPQ-ABL1, which was 1 of 105 cases screened. The relapse observation is from a handful of patients in a retrospective review and is not a trial result.

    Evidence that argues against this (2)
    • This is a rare lesion and the numbers are small enough that a uniform junction across six cases can be a reporting artefact as easily as a biological constraint: cases are found by assays designed around known junctions, so an identical exon 9 / exon 4 breakpoint in every reported case may partly reflect how they were detected. The 0-of-55 paediatric result also bounds nothing strongly at that sample size.
    • SFPQ-ABL1 is a B-cell precursor ALL lesion but is NOT a KMT2A-rearranged lesion, and this graph's index disease is infant KMT2A::AFF1 B-ALL. The shared lineage makes the comparison interesting; it does not make SFPQ-ABL1 a model of the index disease, and the two fusions share no component protein.
  4. E3bmoderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    SFPQ-ABL1 and BCR-ABL1 drive B-ALL by measurably different mechanisms despite sharing the ABL1 kinase. SFPQ-ABL1, identified in a child with Ph-like ALL, was sufficient to transform cytokine-dependent cell lines and those cells were sensitive to ABL1-targeting TKIs. In contrast to BCR-ABL1, SFPQ-ABL1 localised to the NUCLEAR compartment and was a WEAKER driver of cellular proliferation. Phosphoproteomics showed up-regulation of cell cycle, DNA replication and spliceosome pathways and down-regulation of signal transduction pathways including ErbB, NF-kB, VEGF and MAPK relative to BCR-ABL1-expressing cells; SFPQ-ABL1 did not activate PI3K/AKT and was associated with phosphorylation of G2/M cell-cycle proteins. It was sensitive to navitoclax and S-63845 and promoted survival by maintaining Mcl-1 and Bcl-xL expression. The authors conclude that the findings 'highlight the role that fusion partners have in mediating the function of ABL1 fusions'.

    What this evidence cannot show

    Abstract-level only; the full text, the figures and the phosphoproteomic tables were not read, so effect sizes, the number of replicates, and which comparisons were statistically supported are not established here. The system is ECTOPIC EXPRESSION of each fusion in cytokine-dependent cell lines, not patient cells, so every contrast - localisation, proliferation rate, pathway set - is measured in a construct-overexpression setting and the two fusions may not have been expressed at comparable levels; the abstract does not say. 'Nuclear compartment' is the abstract's phrase; no subnuclear body is specified and none should be inferred. The index case is a single child. Title, journal, year, DOI and first author verified live by efetch 2026-09-22.

    Evidence that argues against this (2)
    • The comparison cuts against a simple 'partner sets the address' story as much as for it. SFPQ-ABL1 is a WEAKER proliferative driver that fails to activate PI3K/AKT, so if the partner is doing the work, it is doing less of it: the nuclear address comes with reduced signalling output, not a redirected oncogenic programme of equal strength. A reading in which the partner merely sequesters the kinase away from its cytoplasmic substrates fits these data too, and the abstract does not distinguish the two.
    • Both fusions remained TKI-sensitive, which is the clinically decisive property and is UNCHANGED by the partner. An entry using this paper to argue that the 5' partner determines therapeutic vulnerability would be overstating it: the partner changed the pathway map and the apoptotic dependency (Mcl-1/Bcl-xL, navitoclax, S-63845), but the kinase remained the actionable target in both.
  5. E4moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    SFPQ-ABL1 and RCSD1-ABL1 are the ABL1 fusions characterised by a break in intron 4 of ABL1, with the consequence that the chimeric proteins LACK the SH2 domain of ABL1, and both are associated with B-cell ALL. Across ABL1 fusions generally the kinase domain is always retained and the chimaera also carries the N-terminal part of the partner protein, which often includes a coiled-coil or helix-loop-helix domain; these domains allow oligomerisation of the protein, which is required for tyrosine kinase activation, cytoskeletal localisation and neoplastic transformation. At the time of the review six genes other than BCR were known to fuse to ABL1, and NUP214-ABL1 was the second most prevalent ABL1 fusion in malignant haemopathies at 5% of T-cell ALL.

    ABL1 fusion genes in hematological malignancies: a review. · De Braekeleer E, et al. · European Journal of Haematology 2011
    What this evidence cannot show

    A 2011 REVIEW, abstract-level, and the field has moved: 'six other genes' and the ABL-class fusion catalogue are both out of date, and this is cited for the structural logic of the intron-4 break and the general oligomerisation rule, not as a current census. The oligomerisation statement is explicitly the GENERAL pattern across ABL1 fusion partners, qualified in the source by 'often' - it is NOT a claim that SFPQ contributes a coiled-coil or HLH domain, and the UniProt fields fetched for E1 returned no such annotation for SFPQ. What the SFPQ moiety contributes to SFPQ-ABL1 is an open question in this entry, not a recorded fact.

    Evidence that argues against this (1)
    • The SH2 deletion gives a rival explanation for E3b's findings that does not involve the partner's own properties at all. SH2 is a phosphotyrosine-binding module that shapes ABL1 substrate selection and processive phosphorylation, so a chimaera lacking it might show an altered phosphoproteome and weaker proliferative drive for reasons entirely internal to the truncated kinase - no partner-mediated relocalisation required. E3b's nuclear localisation is not explained this way, but the pathway and potency differences may be. Nothing in this graph separates the two explanations.
  6. E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    SFPQ is a verified component of the HEXIM1-DNA-PK-paraspeckle components-ribonucleoprotein complex (HDP-RNP), a ribonuclear complex built around HEXIM1 and the long non-coding RNA NEAT1 and identified by immunoprecipitation, mass spectrometry and RNA sequencing. The HDP-RNP contains the DNA-PK subunits DNA-PKcs, Ku70 and Ku80 together with the paraspeckle proteins SFPQ, NONO, PSPC1, RBM14 and MATRIN3; binding of HEXIM1 to NEAT1 is required for its assembly, and the complex is required for the innate immune response to foreign DNA through the cGAS-STING-IRF3 pathway.

    HEXIM1 and NEAT1 Long Non-coding RNA Form a Multi-subunit Complex that Regulates DNA-Mediated Innate Immune Response. · Morchikh M, Cribier A, Raffel S, et al. · Molecular Cell 67:387-399.e5 2017
    What this evidence cannot show

    This citation was already stored in `gene-hexim1` (E_q65_loc1) and was RE-FETCHED live on 2026-09-22 rather than copied: PMID, title, journal, year, DOI and first author all confirmed, and the abstract confirmed to name SFPQ, NEAT1 and paraspeckles. The complex was characterised in the context of innate immune signalling, not leukaemia, and nothing in this paper concerns KMT2A, a fusion, or a leukaemic cell. It is cited here to source SFPQ's paraspeckle-protein status, which UniProt's own subcellular-location field does not state.

    Evidence that argues against this (1)
    • Membership of an immunoprecipitated ribonucleoprotein is not evidence of residence in a paraspeckle BODY, and the paper's own naming - 'paraspeckle components' - describes the proteins' provenance rather than the complex's location. Calling SFPQ a paraspeckle protein on this basis is standard usage but is one inferential step from what was measured, and UniProt independently assigns it to nuclear speckles and the nuclear matrix.
Connected to