Oncofusion

start / graph / gene-foxp1

Genemoderate confidence 3 of 5: One strong study, or several smaller consistent ones.Q119-genes-the-measurement-named

FOXP1 - the forkhead repressor that licenses the pro-B to pre-B transition and blocks apoptosis with NF-kB, sitting at a 105x MLL1-N bin in a leukaemia whose defining lesion is a pro-B arrest

also called QRF1 · 12CC4 · HSPC215 · hFKH1B · Forkhead box protein P1 · PAX5::FOXP1 3' partner

FOXP1 is a switch that lets an immature B cell move to its next developmental step, and it also keeps B cells alive by silencing the genes that would make them die. That matters here because infant t(4;11) leukaemia is a B cell stuck at exactly the step FOXP1 controls.

The same thing, for a scientist

**Written because the Q118 measurement named it and the corpus had no entry, and because of all six genes this one lands squarely on the disease's defining cell state.** **Identity, fetched before it was written.** **Q9H334**, `FOXP1_HUMAN`, **677 aa**, `ENSG00000114861`, **HGNC:3823**, cytoband **3p13**, GRCh37 chr3:71,003,844-71,633,140 on the **minus** strand, GRCh38 chr3:70,954,693-71,584,009 [E1][E2]. Aliases `QRF1`, `12CC4`, `HSPC215`, `hFKH1B`; no previous official symbol. Feature table: **C2H2-type zinc finger 306-331, FoxP leucine-zipper (ZIP) 332-372, forkhead DNA-binding domain 465-555**, and a **CTBP1-binding region at 382-386**. UniProt localises it to the **nucleus** and calls it a transcriptional repressor and *essential transcriptional regulator of B-cell development* [E1]. **The developmental result is exactly at this disease's arrest point.** Foxp1-null mice have a profound defect in early B-cell development: decreased expression of all B-lineage genes in B220+ fetal liver cells and **a block in the transition from pro-B to pre-B**, with diminished *Rag1* and *Rag2*; Foxp1 binds the **Erag** enhancer and controls immunoglobulin heavy-chain V(D)J recombination in a B-lineage-specific way [E3]. **KMT2A::AFF1 infant ALL is a pro-B-arrested leukaemia** and this graph carries `cell-state-pro-b-arrest` and `cell-type-pro-b` for that reason. FOXP1 is the transcription factor whose loss *produces* that arrest in a normal animal - which makes it a candidate for either arm of the argument, and the entry does not pick one. **The survival result is an NF-kB result.** FOXP1 **directly represses seven pro-apoptotic genes** - the BH3-only proteins **BIK** and **Harakiri (HRK)**, the p53-regulatory proteins **TP63**, **RASSF6** and **TP53INP1**, plus **AIM2** and **EAF2** - low expression of which is associated with poor survival in DLBCL; FOXP1 promotes expansion of primary mature human B cells by inhibiting caspase-dependent apoptosis without affecting proliferation, and is **dependent upon and cooperates with NF-kB signalling** to do so [E4]. In mature B cells Foxp1 also supports survival through **Bcl2l1/Bcl-xL**, and transgenic BCL2 rescues the Foxp1-deficient survival defect [E5]. This graph already holds an NF-kB folder and `cell-state-apoptotic-priming-bcl2`, and this is a direct join between them. **FOXP1 is also a fusion partner in B-ALL in its own right** - `PAX5::FOXP1` from t(3;9)(p13;p13) is a rare but recurrent, non-random aberration in childhood and adult B-ALL, proposed to contribute by blocking differentiation to mature B cells, and FOXP1 is separately reported as an ABL1 fusion partner in ALL [E6]. **And the measurement that named it.** In RS4;11 the hg19 bin **chr3:71,630,000** reaches **105.2x** the MLL1-N track's own genome median; under VTP-50469 its MLL1-N within-sample share ratio is **0.509** and MENIN **0.052** [E7]. Because FOXP1 is on the minus strand, the bin sits **1.1-3.1 kb from the FOXP1 transcription starts**, i.e. at the promoter and not, as the raw coordinate ordering would suggest, at the 3' end of the gene [E8]. THE ANTIBODY IS NOT FUSION-SPECIFIC: `MLL1n` is Bethyl A300-086A, an MLL1 **N-terminus** epitope retained in KMT2A::AFF1, read with wild-type MLL1 at a masking factor of 3.54-4.00x.

What it looks like
FOXP1677 aa
C2H2C2H2-type zinc finger · residues 306–331FoxPFoxP leucine zipper (ZIP, dimerisation) · residues 332–372CTBP1-binding region · residues 382–386Fork-head (DNA binding)Fork-head (DNA binding) · residues 465–5550200400600

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
The strand trap, and why it is worth a section

FOXP1 spans GRCh37 chr3:71,003,844-71,633,140 on the minus strand. A naive containment check reports the Q118 bin at chr3:71,630,000 as "626 kb into the gene from its start" - deep in the gene body, an unremarkable intragenic signal. That reading is an artefact of comparing a bin to start on a minus-strand gene. Resolved per transcript 8:

transcriptGRCh37 TSSdistance from bin centre
ENST0000049815471,631,1041,104 bp
ENST0000049308971,632,9042,904 bp
ENST0000031877971,633,0903,090 bp
ENST0000031878971,633,1403,140 bp

The bin is at the promoter. This project has already paid for one coordinate error of this family (Q117's UCSC longest-match placing Hoxa9 on chr1), and the fix is the same: resolve per transcript from a stable gene id, and read the strand before reading the offset. Two of the six genes in this beat - FOXP1 and SATB1 - are minus-strand, so the trap is live in a third of the set.

Two readings of FOXP1 at a pro-B-arrested leukaemia, and this entry refuses to choose

Reading A - FOXP1 is part of the arrest. Foxp1 loss blocks pro-B to pre-B and shuts down Rag1/Rag2 and the Erag enhancer 3. A KMT2A::AFF1 blast is a pro-B-arrested cell. If the fusion's programme reduced FOXP1 output, the arrest would be partly explained by a mechanism with a clean knockout phenotype behind it.

Reading B - FOXP1 is part of the survival. FOXP1 represses BIK, HRK, TP63, RASSF6, TP53INP1, AIM2 and EAF2 and cooperates with NF-kB to block caspase-dependent apoptosis 4; in mature B cells it supports Bcl-xL 5. If the fusion's programme raised FOXP1 output, that is an anti-apoptotic dependency, and it would sit directly beside this graph's venetoclax and apoptotic-priming content.

These predict opposite signs and nothing here distinguishes them, because the only KMT2A::AFF1-adjacent datum is a chromatin-occupancy bin from an antibody that cannot attribute occupancy to the fusion, with a VTP-50469 share ratio of 0.509 that is mid-range and uninformative. The distinguishing measurement is trivial and public: FOXP1 transcript level in KMT2A::AFF1 blasts versus normal pro-B cells, and its direction of change under a menin inhibitor. Neither was run here, and FOXP1[tiab] AND "infant"[tiab] returns 1 record, which is about plasticiser exposure and autism 9.

Cell type, cell state, localization

Cell type. B-lineage throughout - B220+ fetal liver pro-B cells, pro-B and pre-B, follicular and B-1 B cells, germinal-centre B cells (where FOXP1 must be downregulated for normal GC function), plasma cells (where it represses differentiation), and DLBCL/MALT lymphoma where it is an oncogene. Outside B cells: monocytes and macrophages via CSF1R, T follicular helper cells (negatively regulated), lung epithelium, cardiac muscle, spinal motor neurons, and embryonic stem cells through a distinct isoform with its own DNA-binding preference 1.

Cell state. The states FOXP1 defines are the pro-B to pre-B transition and apoptotic resistance in an NF-kB-dependent B cell. Both are states this graph already carries entries for (cell-state-pro-b-arrest, cell-state-apoptotic-priming-bcl2), which is unusual for a gene with no entry until today.

Subcellular. Nucleus (UniProt) 1. Subnuclear: not established. No FOXP1 subnuclear imaging was fetched and read this session. The one structural hint in the record is the CTBP1-binding region at 382-386 and the FoxP leucine zipper at 332-372, which mediates FOXP homo- and heterodimerisation - i.e. FOXP1's known higher-order behaviour is dimerisation and corepressor recruitment, not compartment residence, and this entry asserts nothing further.

Facts and figures
gene symbolFOXP1
hgnc IDHGNC:3823
uniprotQ9H334
length AA677
ensemblENSG00000114861
cytoband3p13
locus grch37chr3:71,003,844-71,633,140 (MINUS strand), Ensembl ENSG00000114861, fetched 2026-09-23
locus grch38chr3:70,954,693-71,584,009 (MINUS strand)
roleForkhead-family transcriptional repressor. Essential for the pro-B to pre-B transition and for IgH V(D)J recombination via the Erag enhancer; represses seven pro-apoptotic genes and cooperates with NF-kB to block caspase-dependent apoptosis in B cells; supports Bcl-xL in mature B cells; oncogene in ABC-DLBCL and MALT lymphoma; a rare recurrent fusion partner in B-ALL (PAX5::FOXP1, ABL1::FOXP1).
accession resolutiongene_exact:FOXP1 AND organism_id:9606 AND reviewed:true returned exactly ONE reviewed record (Q9H334, 677 aa), so rule 62 does not fire. data/symbol-collisions.json (208 rows) word-boundary grepped for FOXP1 before the first query: no row. HGNC lists no previous official symbol, so rule 69 does not apply. A FAMILY collision hazard is recorded in E1 and is NOT in the registry: FOXP1-4 heterodimerise through a shared leucine zipper and FOXP3 dominates any loose FOXP search.
epigenetic readoutNOT ESTABLISHED FOR THIS GENE AS A PROTEIN. FOXP1 is a sequence-specific repressor that recruits corepressors (CTBP1 via 382-386, NCOR2 at CSF1R) rather than a reader or writer of any histone mark, so the honest entry for this field is a corepressor-recruitment mechanism and not a mark. The epigenetic content that IS measured here is at the FOXP1 LOCUS: MLL1-N-reactive occupancy at 105.2x over the track's own genome median at its promoter in RS4;11, collapsing to a 0.509 within-sample share under a menin inhibitor.
subcellular localizationNucleus (UniProt Q9H334 SUBCELLULAR LOCATION comment).
subnuclear localizationNOT ESTABLISHED. No FOXP1 subnuclear imaging or fractionation experiment was fetched and read this session, and none is asserted. The only higher-order structure in the record is the FoxP leucine zipper (332-372), which mediates FOXP homo- and heterodimerisation, and the CTBP1-binding region (382-386).
cell typeB-lineage throughout: B220+ fetal liver pro-B cells, pro-B and pre-B, follicular and B-1 B cells, germinal-centre B cells (where it must be downregulated), plasma cells (where it represses differentiation), DLBCL and MALT lymphoma. Outside B cells: monocytes/macrophages (CSF1R), T follicular helper cells, lung epithelium, cardiac muscle, spinal motor neurons, embryonic stem cells.
cell stateThe two states FOXP1 defines are the PRO-B TO PRE-B TRANSITION (Foxp1-null blocks it, with Rag1/Rag2 down and the Erag enhancer unbound) and APOPTOTIC RESISTANCE IN AN NF-kB-DEPENDENT B CELL (seven pro-apoptotic genes directly repressed; Bcl-xL supported). Both correspond to existing nodes in this graph, cell-state-pro-b-arrest and cell-state-apoptotic-priming-bcl2.
shown for fusionNO - nobody has looked in any KMT2A fusion. FOXP1[tiab] AND KMT2A[tiab] returns 4 records and none concerns a fusion-target relationship; FOXP1[tiab] AND "MLL-AF4"[tiab] returns 0. The only KMT2A::AFF1-adjacent datum is an MLL1 N-terminus ChIP bin at its promoter in RS4;11 that cannot distinguish the fusion from wild-type MLL1. FOXP1 IS a fusion partner in B-ALL in its own right (PAX5::FOXP1), which is a different claim.
analogous fusion familiesPAX5::FOXP1 from t(3;9)(p13;p13) places FOXP1 in the B-ALL fusion landscape as a 3' partner, alongside the PAX5 fusion family this graph touches through fusion-tcf3-pbx1 and fusion-etv6-runx1 comparators; ABL1::FOXP1 places it in the kinase-fusion landscape beside fusion-bcr-abl1. In both cases the proposed mechanism is a differentiation block - the same output as the KMT2A fusions, by a different route.
absence classmeasured-not-analysed
absence class noteThe gap that matters is the DIRECTION of FOXP1 expression change in KMT2A::AFF1 blasts relative to normal pro-B cells, and under a menin inhibitor - because the two published FOXP1 biologies predict opposite signs and neither can be chosen without it. That is measured-not-analysed: KMT2A-rearranged and infant-ALL expression compendia are public and this join has not been run. A second, more expensive arm is never-measured: no FOXP1 ChIP, no FOXP1 knockdown and no FOXP1 dependency arm exists in any KMT2A-rearranged cell, and FOXP1[tiab] AND KMT2A[tiab] returns 4 records of which none concerns a fusion-target relationship.
archive check 2026 09 23GEO: GSE127507 supplies the RS4;11 occupancy in E7. No GEO, SRA or expression-compendium query was run for FOXP1 transcript level in KMT2A-rearranged versus normal pro-B cells, so the primary gap above is recorded as UNRUN rather than as bounded - naming the query that would close it, not claiming it was tried.
domains
C2H2-type zinc finger306.0C2H2-type zinc finger: 306FoxP leucine zipper (ZIP,…332.0FoxP leucine zipper (ZIP, dimerisation): 332CTBP1-binding region382.0CTBP1-binding region: 382Fork-head (DNA binding)465.0Fork-head (DNA binding): 465
domains — the numbers behind the chart
[
  {
    "name": "C2H2-type zinc finger",
    "start": 306,
    "end": 331
  },
  {
    "name": "FoxP leucine zipper (ZIP, dimerisation)",
    "start": 332,
    "end": 372
  },
  {
    "name": "CTBP1-binding region",
    "start": 382,
    "end": 386
  },
  {
    "name": "Fork-head (DNA binding)",
    "start": 465,
    "end": 555
  }
]
literature bound 2026 09 23
{
  "FOXP1[tiab]": 1073,
  "FOXP1[tiab] AND KMT2A[tiab]": 4,
  "FOXP1[tiab] AND MLL[tiab]": 2,
  "FOXP1[tiab] AND leukemia[tiab]": 39,
  "FOXP1[tiab] AND \"acute lymphoblastic\"[tiab]": 10,
  "FOXP1[tiab] AND \"pro-B\"[tiab]": 4,
  "FOXP1[tiab] AND \"B cell development\"[tiab]": 18,
  "FOXP1[tiab] AND \"infant\"[tiab]": 1,
  "FOXP1[tiab] AND \"MLL-AF4\"[tiab]": 0,
  "bounded_by": "titles and abstracts only; supporting figures not searched (rule 80). One tag per term, no parenthesised group (rule 94). The four KMT2A hits were read at title level and none concerns a fusion-target relationship."
}
q118 measurement
{
  "series": "GSE127507 (SubSeries of GSE127508, PMID 31821784)",
  "cell_line": "RS4;11",
  "fusion": "KMT2A::AFF1",
  "genome_build": "hg19",
  "bin": "chr3:71,630,000",
  "mll1n_enrichment_over_own_genome_median": 105.2,
  "mll1n_share_ratio_vtp_over_dmso": 0.509,
  "menin_share_ratio_vtp_over_dmso": 0.052,
  "promoter_resolved_here": "1,104 bp from the nearest FOXP1 TSS (ENST00000498154, GRCh37 chr3:71,631,104) and 3,140 bp from ENST00000318789. FOXP1 is on the MINUS strand, so a naive comparison against the gene's start coordinate misreads this bin as 626 kb into the gene body.",
  "antibody": "MLL1n = Bethyl A300-086A, MLL1 N-terminus, epitope RETAINED in KMT2A::AFF1; MENIN = Bethyl A300-105A Lot 8. Neither is fusion-specific.",
  "fusion_specific": false,
  "source_entry": "ana-q118-instrument-check-the-top-rs4-11-mll1-n-bins-are-jmjd1c-cdk6-myb-runx2-and-igf2bp2"
}
How this could bite us back
  • If FOXP1 turns out to be a dependency in KMT2A::AFF1, targeting it means suppressing the transcription factor that normal B-cell development requires at exactly the same stage. The on-target consequence in a healthy compartment is a pro-B-to-pre-B block - i.e. the drug would reproduce the disease's own defining lesion in the patient's remaining normal B lymphopoiesis.
  • FOXP1's anti-apoptotic mechanism runs partly through Bcl-xL, which venetoclax does not inhibit. A FOXP1-high blast would therefore be a candidate venetoclax non-responder for a reason invisible to BH3 profiling that scores BCL2 dependence, and this graph's venetoclax content does not currently carry that route.
  • FOXP1 is required in lung epithelium, cardiac muscle, spinal motor neurons, monocytes and hair-follicle stem cells. Any systemic FOXP1-directed agent has a toxicity surface spanning five organ systems with published knockout phenotypes in each, which is an unusually well-documented reason not to pursue it as a direct target.
Still open
  1. Is FOXP1 up or down in KMT2A::AFF1 blasts relative to normal pro-B cells? The two published FOXP1 biologies - licensing the pro-B to pre-B transition, and blocking apoptosis with NF-kB - predict opposite signs for a leukaemia arrested at pro-B, and public expression data can answer it without new material. Until it is answered, FOXP1's presence in this beat is an observation and not an argument.
  2. Does FOXP1 expression move under a menin inhibitor in KMT2A::AFF1? Its promoter loses half its MLL1-N-reactive share under VTP-50469 (0.509) while menin leaves completely (0.052), which is a pattern with no interpretation attached until transcript data is put beside it.
  3. If FOXP1 supports Bcl-xL rather than BCL2, is the FOXP1 axis a venetoclax-RESISTANT anti-apoptotic route in this disease? This graph reasons extensively about venetoclax and BCL2 priming, and BCL-xL is outside venetoclax's selectivity.
  4. Should the symbol-collision registry carry a FOXP-family row? FOXP1-4 heterodimerise through a shared leucine zipper, FOXP3 dominates a loose search, and FOXP1 acts cooperatively with FOXP4 - so a family-level search is not a gene-level search, and the registry has no row for any of them.
Every source behind this entry (9)
  1. E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    FOXP1 is Q9H334 (FOXP1_HUMAN), 677 aa, with a C2H2-type zinc finger at 306-331, a FoxP leucine-zipper domain at 332-372, a forkhead DNA-binding domain at 465-555 and a CTBP1-binding region at 382-386; it is nuclear, is a transcriptional repressor, is an essential transcriptional regulator of B-cell development, represses pro-apoptotic genes and cooperates with NF-kB signalling to promote B-cell expansion, regulates CSF1R in monocytes with NCOR2 as corepressor, negatively regulates T follicular helper differentiation, and a distinct isoform expressed in embryonic stem cells has its own DNA-binding preference.

    UniProtKB Q9H334 (FOXP1_HUMAN), Forkhead box protein P1 · UniProt Consortium · UniProt 2026
    What this evidence cannot show

    Fetched live 2026-09-23 via gene_exact:FOXP1 AND organism_id:9606 AND reviewed:true, which returned exactly ONE reviewed record, so rule 62 does not fire. data/symbol-collisions.json (208 rows) word-boundary grepped for FOXP1 before the first query: no row. NOTE the family collision hazard the registry does not yet carry: FOXP1, FOXP2, FOXP3 and FOXP4 are paralogues that heterodimerise through the same leucine zipper, FOXP3 is the Treg master gene and dominates any loose search, and FOXP1 acts cooperatively with FOXP4 in lung epithelium - so a FOXP-family search is NOT a FOXP1 search. Per rule 91 the papers UniProt cites were not opened.

    Evidence that argues against this (1)
    • UniProt's FUNCTION block for FOXP1 is a list of eleven largely unrelated tissue functions - lung epithelium, cardiac muscle, spinal motor neuron columns, midbrain dopamine identity, hair-follicle stem cell quiescence, angiogenesis, androgen receptor signalling, monocyte differentiation, T follicular helper cells, B cells and ESC pluripotency. A transcription factor with that breadth has no default behaviour, and importing any one of these functions into a leukaemic pro-B cell without a measurement in that cell is unwarranted. Nat Immunol 2006
  2. E2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database

    HGNC assigns FOXP1 (HGNC:3823, 'forkhead box P1') the primary Ensembl gene id ENSG00000114861, cytoband 3p13 and UniProt Q9H334, with alias symbols QRF1, 12CC4, HSPC215 and hFKH1B and no previous symbol; Ensembl places the gene at GRCh37 chr3:71,003,844-71,633,140 and GRCh38 chr3:70,954,693-71,584,009, both on the MINUS strand.

    HGNC record HGNC:3823 (FOXP1) and Ensembl gene ENSG00000114861 on GRCh37 and GRCh38 · HUGO Gene Nomenclature Committee; Ensembl · genenames.org / Ensembl 2026
    What this evidence cannot show

    Fetched live 2026-09-23 and resolved before any sentence using them was written. No previous official symbol, so rule 69 does not apply. The MINUS strand is load-bearing for reading the Q118 bin and is stated here for that reason (see E8).

    Evidence that argues against this (1)
    • An 'absent' alias list is weaker evidence than it looks. HGNC records four aliases for FOXP1 and no previous symbol, which this entry uses to argue that the symbol-based literature bound is not undercounting - but a gene whose paralogues heterodimerise with it through a shared leucine zipper can be discussed under a family name in a title, and no HGNC field records that. The registry has no FOXP-family row, which is itself a gap this entry names. UniProt Consortium 2026
  3. E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper

    Absence of Foxp1 causes a profound defect in early B-cell development, with decreased expression of all B-lineage genes in B220+ fetal liver cells and a block in the transition from pro-B cell to pre-B cell involving diminished expression of Rag1 and Rag2; Foxp1 binds the Erag enhancer and controls V(D)J recombination of the immunoglobulin heavy-chain gene in a B-cell-lineage-specific way.

    Foxp1 is an essential transcriptional regulator of B cell development · Hu H, Wang B, Borde M, Nardone J, Maika S, Allred L, et al. · Nat Immunol 2006
    What this evidence cannot show

    Abstract-level read; the full text was not opened this session. MOUSE germline knockout. The pro-B-to-pre-B block described here is a developmental arrest in a normal animal, which is a different object from the pro-B arrest of a KMT2A::AFF1 blast, and this entry does not claim they share a mechanism - only that they are at the same stage, which is what makes the comparison worth making.

    Evidence that argues against this (1)
    • A conditional deletion from the pro-B stage onwards found deregulation of B-lymphocyte development and function at MULTIPLE stages rather than a single clean block, so the germline phenotype's apparent stage-specificity partly reflects when the gene was removed. A stage assignment from a germline knockout is an upper bound on specificity, not a measurement of it. Immunohorizons 2019
  4. E4strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    FOXP1 directly represses a set of seven pro-apoptotic genes - the BH3-only proteins BIK and Harakiri, the p53-regulatory proteins TP63, RASSF6 and TP53INP1, and AIM2 and EAF2 - whose low expression is associated with poor survival in DLBCL patients; FOXP1 promotes the expansion of primary mature human B cells by inhibiting caspase-dependent apoptosis without affecting proliferation, and it is dependent upon and cooperates with NF-kB signalling to promote B-cell expansion and survival.

    FOXP1 directly represses transcription of proapoptotic genes and cooperates with NF-kB to promote survival of human B cells · van Keimpema M, Grüneberg LJ, Mokry M, van Boxtel R, Koster J, Coffer PJ, et al. · Blood 2014
    What this evidence cannot show

    Abstract-level read; the full text was not opened this session. PRIMARY HUMAN MATURE B CELLS and DLBCL cell lines - not pro-B cells and not leukaemia, so the target set is established in a differentiated compartment and its relevance to a pro-B-arrested blast is an assumption. The DLBCL survival association is correlative.

    Evidence that argues against this (1)
    • FOXP1 must be DOWNREGULATED for normal germinal-centre B-cell function, and it represses plasma-cell differentiation. So the same protein is required for early development, must fall during the GC reaction, and is oncogenic when it fails to fall - its effect is entirely stage-dependent, which means 'FOXP1 is anti-apoptotic in B cells' is not a statement that can be carried into a pro-B blast without measuring it there. Blood 2013
  5. E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper

    Conditional disruption of Foxp1 in developing and mature B cells reduces numbers and frequencies of follicular and B-1 B cells and impairs T-cell-independent antibody responses; Foxp1-deficient B cells are impaired in survival despite an increased capacity to proliferate; transcriptional analysis identifies defective expression of Bcl2l1 (Bcl-xL) with Foxp1 binding in its regulatory region, and transgenic overexpression of Bcl2 rescues the survival defect and restores peripheral B-cell numbers in vivo.

    Foxp1 controls mature B cell survival and the development of follicular and B-1 B cells · Patzelt T, Keppler SJ, Gorka O, Thoene S, Wartewig T, Reth M, et al. · Proc Natl Acad Sci U S A 2018
    What this evidence cannot show

    Abstract-level read; the full text was not opened this session. MOUSE conditional knockout, MATURE B cells. The BCL2 rescue is transgenic overexpression, which demonstrates sufficiency of an anti-apoptotic signal to restore numbers and not that Bcl-xL is the only mediator.

    Evidence that argues against this (1)
    • This graph has no gene-bcl2l1 entry, so the specific anti-apoptotic effector named here cannot be linked, and the nearest node - gene-bcl2 - is a different protein with a different inhibitor profile. Venetoclax does not inhibit BCL-xL, so a FOXP1-Bcl-xL dependency would be a BCL2-inhibitor-RESISTANT anti-apoptotic axis, not a supporting argument for the venetoclax content this graph already holds. Proc Natl Acad Sci U S A 2018
  6. E6moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper

    PAX5-FOXP1, arising from t(3;9)(p13;p13), is a rare but recurrent and non-random translocation in both childhood and adult B-cell acute lymphoblastic leukaemia, proposed to contribute to leukaemogenesis by blocking differentiation of haematopoietic cells into mature B cells; FOXP1 is separately reported as a novel ABL1 fusion partner in acute lymphoblastic leukaemia.

    FOXP1 and PAX5 are rare but recurrent translocations partners in acute lymphoblastic leukemia · Put N, Deeren D, Michaux L, Vandenberghe P · Cancer Genet 2011
    What this evidence cannot show

    Abstract-level read; the source is a SINGLE CASE REPORT (a 57-year-old man with B-ALL) that positions itself as the fifth reported PAX5-FOXP1 case. 'Recurrent' therefore rests on five cases across two age groups, and the leukaemogenic mechanism ('may contribute by blocking differentiation') is the authors' proposal, not a measurement. The ABL1-FOXP1 claim is from a separate report (PMID 21391972) seen at title level only and is named, not characterised.

    Evidence that argues against this (1)
    • Five cases is not a frequency, and a fusion partner list assembled from case reports is shaped by which cytogenetic abnormalities get published. This graph's own epidemiology entries repeatedly find that partner-level claims built on small case series do not survive registry-scale analysis. Iqbal Lab oncofusion knowledge graph 2026
  7. E7moderate confidence 3 of 5: One strong study, or several smaller consistent ones.dataset

    In RS4;11 (KMT2A::AFF1) the hg19 2 kb bin chr3:71,630,000 reaches 105.2x the MLL1-N track's own genome median and is in the top thirty bins genome-wide; under VTP-50469 its MLL1-N within-sample share ratio is 0.509 and its MENIN share ratio is 0.052.

    What this evidence cannot show

    THE MEASUREMENT THAT NAMED THIS GENE IS NOT FUSION-SPECIFIC. The track is MLL1n, Bethyl A300-086A, an MLL1 N-TERMINUS antibody whose epitope is retained in KMT2A::AFF1, so it reads fusion and wild-type MLL1 together at a masking factor the same beat measured as 3.54-4.00x; every statement from it is about MLL1-N-reactive material, never about the fusion. n = 1 per antibody per condition - GSE127507 has no replicate - and the depositors measured a Drosophila spike-in and deliberately did not apply it, so cross-condition figures are within-sample shares. A share ratio of 0.509 is MID-RANGE within the top thirty (which spans 0.091 to 4.036) and is therefore the least informative kind of value this measurement produces: it neither holds nor collapses.

    Evidence that argues against this (1)
    • The MENIN share ratio at this bin is 0.052, i.e. menin leaves as completely as it does everywhere in the held set, while MLL1-N halves. A gene whose menin signal collapses and whose MLL1-N signal partially persists is indistinguishable from a wild-type MLL1 site, which is the single most likely explanation for a bin at a housekeeping-adjacent B-lineage transcription factor promoter. Iqbal Lab oncofusion knowledge graph 2026
  8. E8strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database

    FOXP1 is on the MINUS strand, so its transcription starts are at the high-coordinate end of the gene: on GRCh37 the nearest starts to the bin centre chr3:71,630,000 are ENST00000498154 at 71,631,104 (1,104 bp), ENST00000493089 at 71,632,904, ENST00000318779 at 71,633,090 and ENST00000318789 at 71,633,140 (3,140 bp). The bin is therefore at the FOXP1 promoter region, not deep in the gene body as a naive comparison against the gene's `start` coordinate would suggest.

    What this evidence cannot show

    Fetched live 2026-09-23, resolved from a stable gene id to transcript coordinates rather than by a name lookup. Ensembl gene models, not experimentally mapped start sites in a leukaemic cell. Two of the four nearest starts are processed transcripts rather than protein-coding, and a 2 kb bin cannot distinguish transcripts 2 kb apart, so 'the promoter region' is the strongest claim the resolution supports.

    Evidence that argues against this (1)
    • The naive containment check on this gene initially read the bin as sitting 626 kb 'into' FOXP1 - an intragenic signal - because it compared the position to the gene's low-coordinate `start`. That reading is wrong and it is the kind of wrong that passes review, which is why the per-transcript resolution is recorded as evidence rather than left implicit. Ensembl GRCh37 archive 2026
  9. E9moderate confidence 3 of 5: One strong study, or several smaller consistent ones.database

    Bounded literature counts, 2026-09-23: FOXP1[tiab] 1,073; FOXP1[tiab] AND KMT2A[tiab] 4 (none about a fusion-target relationship - optical genome mapping in AML, a salivary-gland tumour panel, a congenital-heart connectome study and an autism corticostriatal review); FOXP1[tiab] AND MLL[tiab] 2; FOXP1[tiab] AND leukemia[tiab] 39; FOXP1[tiab] AND "acute lymphoblastic"[tiab] 10; FOXP1[tiab] AND "pro-B"[tiab] 4; FOXP1[tiab] AND "B cell development"[tiab] 18; FOXP1[tiab] AND "infant"[tiab] 1 (a plasticiser-and-autism study); FOXP1[tiab] AND "MLL-AF4"[tiab] 0.

    PubMed esearch via scripts/pubmed_safe.py, 2026-09-23 · Q119-genes-the-measurement-named · NCBI PubMed 2026
    What this evidence cannot show

    Bounded by TITLES AND ABSTRACTS only (rule 80). One tag per term, no parenthesised group (rule 94); every querytranslation was read back and each expanded to "TERM"[Title/Abstract]. The KMT2A, pro-B, acute-lymphoblastic, B-cell-development and infant result sets WERE read at title level and are characterised above; the 39 leukemia records were not. This is the cleanest genuine absence in the beat: FOXP1 has a large literature, a large leukaemia literature, and NOTHING connecting it to a KMT2A fusion.

    Evidence that argues against this (1)
    • A bound on titles and abstracts is especially weak for a transcription factor that appears in expression signatures. FOXP1 could be a well-known component of the KMT2A::AFF1 expression programme in a supplementary table of a paper titled after something else, and none of these queries would see it - which is exactly how rule 80 was learned. NCBI PubMed 2026
Connected to