PBX2 - an AFF4 co-purifying protein in two rounds of one AP-MS atlas, and the PBX paralogue the leukaemia literature explicitly excluded
also called PBX2 · G17 · Pre-B-cell leukemia transcription factor 2 · Homeobox protein PBX2 · P40425
PBX2 is one of three closely related proteins that partner HOX transcription factors; this graph's HOXA story is built on its sibling PBX3. PBX2 shows up as a co-purifying protein of AFF4 in a large automated survey of human protein interactions, and the one leukaemia paper that compared the three siblings directly said PBX2 is not the one that matters.
The same thing, for a scientist
PBX2 (UniProt **P40425, 430 aa**, primary gene name read back 2026-09-21) is the third PBC-class TALE homeodomain protein and the only one this graph had not written. It enters the interactome as a **prey of tagged AFF4** in the BioPlex affinity-purification atlas, in **HEK293T**, recorded twice - BioPlex 2.0 (PMID 28514442, `EBI-21673782`) and BioPlex 3.0 (PMID 33961781, `EBI-54610644`) - both spoke-expanded from an AP-MS pulldown, IntAct MI-score 0.53 [E1]. **Provenance first: this is a proteome-scale atlas, not a study of AFF4.** What raises it above the floor is that the same AFF4 pulldown recovers essentially the whole super elongation complex - CCNT1, CCNT2, CDK9, ELL, ELL2, ELL3, EAF1, EAF2, HEXIM1, MLLT1 - so the experiment demonstrably works on this bait [E2]; and that PBX2 is **not a promiscuous prey**, with 27 partners in BioPlex 3.0 and 16 in HuRI against AFF4's own 38 [E2]. What holds it down is that **no focused source exists**: `(AFF4 OR AF4/FMR2) AND (PBX OR PBX2)` returns **0** in titles and abstracts, and the three records joining PBX2 to MLL or KMT2A are all PBX3/HOXA9 papers using PBX2 as a comparator [E3]. **The published counter-evidence is unusually direct.** Li et al. 2013, the Blood paper that grounds `gene-pbx3`, states that *"it is PBX3, but not PBX1 or PBX2, that is consistently coexpressed with HOXA9 in various subtypes of CA-AML, particularly MLL-rearranged AML"* [E4]. And *Pbx2*-null mice are born at Mendelian frequency with no developmental phenotype and **no measurable effect on steady-state haematopoiesis** [E5]. The one fact that keeps PBX2 interesting is in the same knockout paper: **in postnatal bone marrow and thymus, Pbx2 is the predominant high-molecular-weight PBX isoform detectable by immunoblot** [E5]. So the protein is abundant in the tissue this disease arises in, dispensable at steady state, transcriptionally excluded from the HOXA9 argument, and physically near AFF4 in one atlas. The entry is written at `weak` and exists so that the PBX family's third member is visible rather than absent.
This is a prediction, not a measurement. No one has seen this protein in this shape. The colours say how much the software trusts itself, and that is worth reading before anything else — the orange stretches are places the model is effectively saying this part has no fixed shape.
I have never read one of these pictures before
A protein is one long chain of amino acids that folds up. The ribbon traces that chain from one end to the other; it is not a wire, it is a simplification of where the backbone runs. Drag to rotate, scroll to zoom.
Domains are the stretches of chain that do a particular job, and they are what the coloured blocks above the picture mark out. Click one and the view flies to it. In this project the important question about any domain is usually whether the fusion still has it — the labels say lost where it does not.
Anything in yellow sticks is a bound small molecule, which is usually the drug.
What the evidence actually is, and what it is not
It is: tagged AFF4 expressed in HEK293T, immunoprecipitated with an anti-tag antibody, bound proteins identified by mass spectrometry, PBX2 among them, in two independent rounds of the same pipeline seven years apart.
It is not: a binary interaction. Both IntAct rows carry psi-mi:"MI:1060"(spoke expansion) - the pair is IntAct's binarisation of a one-bait pulldown, asserting co-purification with AFF4 and nothing about direct contact. No region is mapped, no affinity is measured, no reciprocal pulldown exists (AFF4 is bait in both rows; PBX2 is never the bait), and there is no structure.
It is also not about the fusion. The bait is wild-type AFF4, not AFF1 and not any KMT2A fusion, in a human embryonic kidney line. AFF4 and AFF1 are paralogous SEC scaffolds and this graph carries a live hypothesis that their neighbourhoods differ (hyp-aff1-and-aff4-occupy-distinct-proximity-neighbourhoods), so an AFF4 result does not transfer to AFF1 for free.
Two rounds is reproduction, not independent replication. BioPlex 2.0 and 3.0 are the same laboratory, the same ORF library, the same cell line and the same method. It rules out a one-off mis-assignment; it does not rule out a systematic property of that pipeline.
The paralogue problem, and a length collision that is worse than the one already logged
data/symbol-collisions.json already carries a row for PBX3, warning that P40424 (PBX1, 430 aa) and P40426 (PBX3, 434 aa) are four residues and one accession digit apart, so verify-accessions.py cannot catch a swap. gene-pbx3's own paralogue_discrimination field says "PBX2 (not resolved this cycle)".
Resolved here, live: P40425, PBX2, 430 aa - exactly the same length as PBX1.
| accession | symbol | length |
|---|---|---|
| P40424 | PBX1 | 430 |
| P40425 | PBX2 | 430 |
| P40426 | PBX3 | 434 |
Three consecutive accessions, two of them identical in length. This is the RAS-family case of brief rule 68, where the length discriminator provides no protection at all, not the four-residue case the existing row describes. gene_primary is the only field that separates PBX1 from PBX2. The registry row should be amended; this beat did not edit that file because a concurrent beat is likely writing to it, and the proposed text is in the memo.
Why this is not simply an argument for PBX3 by another name
This graph's PBX position is myeloid. Li et al. 2013 is cytogenetically abnormal AML; the transformation assays are murine; the PBX3/MEIS1-without-HOXA9 result in mechanism-pbx3-meis1-dimer-transforms-without-hoxa9 is murine myeloid. gene-pbx3 already records this and asks, in its own open questions, whether the PBX3 requirement is a myeloid-lineage property about to be generalised across a lineage boundary for the second time.
PBX2 does not answer that. But it changes the shape of the question, because the only PBX measurement made in bone marrow at the protein level puts PBX2, not PBX3, at the top 5. Li 2013's exclusion of PBX2 is a co-expression argument from transcript data in AML, and a transcript-level exclusion is not a protein-level one - Selleri's immunoblot and Li's expression analysis are measuring different things in different tissues and are not in conflict.
The honest statement is that the PBX family has never been tested combinatorially in any human KMT2A-rearranged cell, and PBX2 has never been tested at all. That is the hypothesis node this beat writes alongside this entry, not a claim made here.
| uniprot | P40425 |
|---|---|
| gene symbol | PBX2 |
| length AA | 430 |
| alphafold ID | AF-P40425-F1 |
| protein class | PBC-class TALE (three-amino-acid-loop-extension) homeodomain transcription factor |
| uniprot resolution | gene_exact:PBX2 AND organism_id:9606 AND reviewed:true returned ONE reviewed row on 2026-09-21; primary gene name read back as PBX2; entry PBX2_HUMAN; 430 aa; sole synonym G17; fields=accession,id,gene_primary,gene_synonym,protein_name,length. |
| paralogue discrimination | P40424 PBX1 430 aa, P40425 PBX2 430 aa, P40426 PBX3 434 aa - three consecutive accessions, and PBX1 and PBX2 are IDENTICAL in length. This is the rule-68 RAS-family case, not the rule-66 four-residue case: verify-accessions.py offers zero protection against a PBX1/PBX2 swap. Discriminate on gene_primary only. The existing data/symbol-collisions.json PBX3 row describes PBX1 vs PBX3 and should be amended to name all three. |
| domains note | No domain boundaries asserted. The PBC-A, PBC-B and TALE homeodomain residue ranges were not read back from UniProt this cycle, and a guessed boundary is invisible to the 3D viewer under the residue-integer rule and wrong under the citation rule. |
| shown for fusion | Nobody has looked in any fusion. The bait is wild-type AFF4 ORF in HEK293T; there is no PBX2 experiment in AFF1, in any KMT2A fusion, or in any haematopoietic cell. |
| why this entry exists | PBX2 was one of 17 bait-supported IntAct partners of the six core proteins with no entry, named in the 2026-09-21 recount. gene-pbx3's own paralogue_discrimination field recorded PBX2 as 'not resolved this cycle', and gene-pbx3's open questions ask for a combinatorial PBX1/PBX2/PBX3 test that cannot be specified while one member is unwritten. |
| subnuclear localization | Nuclear speckles, partial colocalisation with HOXA9 and MEIS1, in myeloid cells (PMID 10082572, abstract-level). No other subnuclear observation of PBX2 exists. |
| localization shown for fusion | NO for the fusion, MYELOID for the lineage. Nobody has localised PBX2 in a KMT2A-rearranged cell: the bounded query returned 0. The nuclear-speckle observation is in myeloid cells expressing HOXA9 and MEIS1 - the programme KMT2A fusions drive - but the cells in PMID 10082572 are NOT KMT2A-rearranged, and this entry must not be read as though they were. |
domains
[]
interaction with the core complex
{
"partner": "AFF4",
"partner_accession": "Q9UHB7",
"our_protein_role": "prey",
"bait": "AFF4 (tagged ORF)",
"method": "psi-mi:\"MI:0007\"(anti tag coimmunoprecipitation)",
"interaction_type": "psi-mi:\"MI:0914\"(association)",
"expansion": "psi-mi:\"MI:1060\"(spoke expansion) - NOT a measured binary interaction",
"host_system": "Homo sapiens HEK293T embryonic kidney cell",
"source_publications": [
"28514442",
"33961781"
],
"source_class": "proteome-scale AP-MS atlas (BioPlex 2.0 and 3.0)",
"intact_acs": [
"intact:EBI-21673782",
"intact:EBI-54610644"
],
"intact_miscore": 0.53,
"reciprocal_pulldown": false,
"region_mapped": false,
"affinity_measured": false,
"structures": [],
"independent_replication": "none - BioPlex 2.0 and 3.0 are the same laboratory, ORF library, cell line and method"
}promiscuity controls 2026 09 21
{
"PBX2_distinct_partners_in_bioplex_3_0": 27,
"PBX2_distinct_partners_in_bioplex_2_0": 19,
"PBX2_distinct_partners_in_huri_luck_2020": 16,
"PBX2_distinct_partners_in_rolland_2014_y2h": 2,
"AFF4_distinct_partners_in_bioplex_3_0": 38,
"interpretation": "PBX2 is not a hub prey in the dataset that reports it, which removes the commonest artefact explanation without establishing specificity.",
"source": "computed from IntAct PSICQUIC MITAB rows per publication, retrieved 2026-09-21"
}counted absences
{
"aff4_x_pbx": {
"query": "(AFF4[tiab] OR AF4/FMR2[tiab]) AND (PBX[tiab] OR PBX2[tiab])",
"records": 0,
"date": "2026-09-21"
},
"pbx2_x_mll": {
"query": "PBX2[tiab] AND (MLL[tiab] OR KMT2A[tiab])",
"records_raw": 3,
"records_on_topic": 0,
"pmids": [
"23264595",
"22902925",
"17942707"
],
"date": "2026-09-21"
},
"operand_controls": {
"PBX2[tiab]": 171,
"AFF4[tiab]": 121,
"PBX2 AND leukemia/leukaemia": 28,
"PBX2 AND (HOXA9 OR MEIS1)": 16
},
"bound": "zero in titles and abstracts; supporting figures not searched; complex-name phrase queries not run"
}localization
{
"subcellular": "Nucleus. NOTE THE EVIDENCE GRADE: UniProt P40425's Nucleus call carries ECO:0000305 ONLY - curator inference, with no experimental citation at all (contrast CtIP's and KMT2A's ECO:0000269 records). HPA immunofluorescence independently gives main location Nucleoplasm, reliability Supported. The experiment UniProt does not cite is PMID 10082572.",
"subnuclear": "NUCLEAR SPECKLES, partial. In myeloid cells HOXA9, MEIS1 and PBX2 are all strongly nuclear and a portion of their signals are colocalised within nuclear speckles (PMID 10082572). This is the only subnuclear observation of PBX2 reachable from a bounded search, and it is in a HAEMATOPOIETIC cell.",
"how_shown": "immunofluorescence colocalisation in myeloid cells, alongside EMSA and co-immunoprecipitation from myeloid nuclear extracts (PMID 10082572); antibody immunofluorescence in HPA's non-haematopoietic panel",
"tissue_of_evidence": "myeloid cells for the speckle result; non-haematopoietic lines for HPA",
"rule_91_note": "UniProt's P40425 record cites NO paper for PBX2's location, and the paper that reports one - a 1999 Mol Cell Biol study whose own abstract states the nuclear and speckle result - is absent from the record. Read the uncoded comment, then go and find the experiment.",
"full_text_not_retrievable": "PMID 10082572 is PMC84099 and marked inEPMC; the Europe PMC fullTextXML endpoint returned HTTP 500 and the PMC HTML route returned a stub on 2026-09-21. This record is therefore ABSTRACT-LEVEL. The abstract states the result verbatim; the cell line, the antibody and the speckle marker are NOT recoverable from it.",
"node": "localization-nuclear-speckles-kmt2a-r"
}cell type
{
"haematopoietic_answer": "MYELOID CELLS. PBX2 is strongly expressed in the nucleus of myeloid cells and is the PBX protein recovered in HOXA9-MEIS1 trimeric complexes from myeloid nuclear extracts by EMSA and co-immunoprecipitation (PMID 10082572).",
"why_this_matters_here": "The HOXA9/MEIS1 axis is the programme KMT2A fusions drive. The entry previously held PBX2 only as an AFF4 AP-MS co-purifier in HEK293T with no haematopoietic experiment. There is one, it is from 1999, and it puts PBX2 inside this graph's central transcriptional module - as the PBX protein, in myeloid cells, in nuclear speckles.",
"CONTRADICTION_WITH_AN_ATLAS": "The Human Protein Atlas Blood Atlas records PBX2 as Not detected in immune cells with blood cell distribution Not detected. That is flatly at odds with strong nuclear PBX2 protein in myeloid cells. Both can be literally true - HPA measures RNA in sorted NORMAL peripheral-blood immune cells, and PMID 10082572 measures protein in transformed myeloid cells - but the tension is real and is recorded here rather than resolved. Do not quote either without the other.",
"paralogue_discipline": "The collision registry's PBX2 row applies: PBX1 and PBX2 are BOTH 430 aa, so the length check gives zero discrimination, and PMID 23361910 explicitly excludes PBX2 from the PBX3 finding. PMID 10082572 names PBX2 in its title and abstract, so this record is safe - but nothing may be carried here from a PBX1 or PBX3 result."
}cell state
{
"state": "HOXA9/MEIS1-co-expressing transformed myeloid state. The complexes were recovered from myeloid cells co-expressing HOXA9 and MEIS1, the combination sufficient to induce murine myeloid leukaemia (PMID 10082572).",
"not_established": "No PBX2 cell-state experiment exists in B lineage, in KMT2A::AFF1, or in normal haematopoiesis."
}localization bounded absence
{
"date": "2026-09-21",
"tool": "NCBI E-utilities esearch, db=pubmed",
"shape": "gene clause AND localisation clause AND KMT2A/MLL-fusion clause, one [tiab] tag per term (brief rule 94), every cytogenetic term quoted (brief rule 95)",
"querytranslation_fusion_clause": "\"KMT2A\"[Title/Abstract] OR \"MLL\"[Title/Abstract] OR \"MLL1\"[Title/Abstract] OR \"MLL-AF4\"[Title/Abstract] OR \"MLL-AF9\"[Title/Abstract] OR \"MLL-ENL\"[Title/Abstract] OR \"KMT2A-rearranged\"[Title/Abstract] OR \"MLL-rearranged\"[Title/Abstract] OR \"t 4 11\"[Title/Abstract] OR \"t 9 11\"[Title/Abstract] OR \"MLL fusion\"[Title/Abstract]",
"count": 0,
"controls": {
"fusion_clause_alone": 8743,
"gene_clause_alone": 861
},
"reading": "Zero in TITLES AND ABSTRACTS only; supporting figures were not searched (brief rule 80)."
}- The HXR9 peptide this graph carries as target-hox-pbx-interface-peptide-hxr9 disrupts HOX-PBX interactions through the conserved hexapeptide groove, which is shared across PBX1, PBX2 and PBX3. A strategy justified on PBX3 will hit PBX2 as well, and PBX2 is the dominant high-molecular-weight PBX in normal bone marrow - so the on-target normal-tissue exposure of a pan-PBX agent is larger than a PBX3-framed rationale implies.
- If PBX2 does compensate for PBX3, a PBX3-selective intervention has a built-in escape that no published experiment is positioned to see, because no study has depleted more than one PBX paralogue at a time in this disease.
- Equally: nothing in this entry supports treating PBX2 as a target. It is recorded at weak confidence precisely so that a later reader does not upgrade an AP-MS prey into a partner by association with PBX3.
- Is PBX2 protein present in human KMT2A::AFF1 B-lineage blasts, and at what level relative to PBX1 and PBX3? Selleri's immunoblot says PBX2 dominates the high-molecular-weight PBX pool in murine bone marrow, and no equivalent measurement exists in this disease in either species. A three-lane blot in SEM and RS4;11 would settle it.
- Does endogenous PBX2 co-immunoprecipitate with endogenous AFF1 or AFF4 in a leukaemia line, or is the BioPlex hit a property of overexpressed tagged ORFs in HEK293T? This is the single experiment that would move the entry off 'weak'.
- Li 2013 excluded PBX2 on transcript coexpression in AML. Does that exclusion hold at the protein level, and does it hold in B-lineage KMT2A::AFF1 rather than myeloid CA-AML? The graph's whole PBX position rests on a myeloid comparison that has never been repeated in the index lineage.
- PBX2 is in nuclear speckles in myeloid cells (PMID 10082572, 1999, never replicated) and this graph already holds localization-nuclear-speckles-kmt2a-r. Is PBX2 in speckles in a KMT2A::AFF1 B-lineage blast, and does it move under a menin inhibitor? One immunofluorescence in SEM or RS4;11 would answer a question left open for twenty-seven years.
- Why does the Blood Atlas call PBX2 undetected in normal immune cells while a 1999 study reports strong nuclear PBX2 protein in myeloid cells? If PBX2 protein is genuinely absent from normal blood and present in transformed myeloid cells, that is a tumour-restricted expression pattern and nobody has said so.
- E1moderate confidence 3 of 5: One strong study, or several smaller consistent ones.database
IntAct records PBX2 as a prey of bait AFF4 in two anti-tag coimmunoprecipitation experiments in HEK293T, from BioPlex 2.0 (PMID 28514442) and BioPlex 3.0 (PMID 33961781), both spoke-expanded, MI-score 0.53.
IntAct molecular interaction database, PSICQUIC MITAB 2.7, query id:P40425 AND id:Q9UHB7, 2 rows retrieved 2026-09-21 · IntAct (EMBL-EBI) 2026What this evidence cannot show
Spoke expansion means neither row is a measured binary interaction; both assert co-purification with the bait. The two rows are the same laboratory, ORF library, cell line and method seven years apart, so they are a reproduction rather than an independent replication. HEK293T is not a haematopoietic cell and the bait is wild-type AFF4, not AFF1 and not a KMT2A fusion.
Evidence that argues against this (1)
- An AP-MS prey list from a proteome-scale atlas contains a known background of abundant and sticky proteins, and PBX2 is a nuclear DNA-binding protein of the class that co-purifies with chromatin-associated baits for reasons unrelated to specific contact. Neither BioPlex round reports a reciprocal pulldown with PBX2 as bait. Huttlin EL et al. 2017
- E2strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
The BioPlex 3.0 AFF4 pulldown that reports PBX2 also recovers CCNT1, CCNT2, CDK9, ELL, ELL2, ELL3, EAF1, EAF2, HEXIM1 and MLLT1, and PBX2 is a modest-degree prey with 27 distinct partners in BioPlex 3.0 and 16 in HuRI.
Dual proteome-scale networks reveal cell-specific remodeling of the human interactome. · Huttlin EL, Bruckner RJ, Navarrete-Perea J, et al., Gygi SP · Cell 2021What this evidence cannot show
Partner counts were computed from IntAct's holdings of each publication on 2026-09-21, not from the papers' own supplementary tables, and IntAct's import may not be complete. Recovering the SEC validates the bait, not the individual prey: a pulldown can be simultaneously correct about its core complex and wrong about a peripheral hit. The degree figures bound promiscuity within these datasets only.
Evidence that argues against this (1)
- A low prey degree is weak reassurance. A protein can be a specific contaminant of one bait class - here, chromatin- and elongation-associated baits - and still have few partners overall, which is indistinguishable from specificity in a dataset of this design. Rolland T et al. 2014
- E3strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.database
No focused literature joins PBX2 to AFF4 or to KMT2A: (AFF4[tiab] OR AF4/FMR2[tiab]) AND (PBX[tiab] OR PBX2[tiab]) returns 0 records, and PBX2[tiab] AND (MLL[tiab] OR KMT2A[tiab]) returns 3, all of which title-check to PBX3/HOXA9/MEIS1 papers in which PBX2 appears only as a comparator.
PubMed counted-absence searches for PBX2 against AFF4, MLL and KMT2A, run 2026-09-21 · PubMed (NCBI) 2026What this evidence cannot show
Operand controls were run and the instrument is working: PBX2[tiab] alone returns 171, AFF4[tiab] alone returns 121, PBX2[tiab] AND leukemia OR leukaemia returns 28, PBX2[tiab] AND (HOXA9[tiab] OR MEIS1[tiab]) returns 16. Both querytranslations expanded as written. The three MLL/KMT2A records are PMID 23264595 (PBX3 is an important cofactor of HOXA9 in leukemogenesis), 22902925 (DACH1 and HOXA9 in MLL-AF9) and 17942707 (Meis1 in MLL leukaemia stem cells). Zero in titles and abstracts; supporting figures were not searched, and a complex-level phrase query such as 'super elongation complex' AND PBX was not run.
Evidence that argues against this (1)
- Brief rule 80 is the live risk here: the measurement that would matter - a PBX2 blot in a PBX-family panel from a KMT2A-rearranged cell - is exactly the kind of supporting figure that a title/abstract index cannot reach. The count bounds what is findable by symbol, not what has been done. Li Z et al. 2013
- E4strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
In cytogenetically abnormal AML including MLL-rearranged AML, it is PBX3 and not PBX1 or PBX2 that is consistently coexpressed with HOXA9, and depletion of Pbx3 inhibits MLL-fusion-mediated transformation.
PBX3 is an important cofactor of HOXA9 in leukemogenesis. · Li Z, Zhang Z, Li Y, et al., Chen J · Blood 2013What this evidence cannot show
Read as abstract, not full text. The system is cytogenetically abnormal AML - myeloid, not the B-lineage infant KMT2A::AFF1 disease this graph is about - and the transformation assays are murine. The exclusion of PBX2 is a transcript coexpression argument; it is not a protein measurement and it is not a functional test of PBX2. This is the paper that grounds gene-pbx3 and it is cited in 5 entries here.
Evidence that argues against this (1)
- A coexpression argument cannot exclude a protein that is present without being transcriptionally co-regulated. Selleri et al. 2004 report by immunoblot that Pbx2 is the predominant high-molecular-weight PBX protein in postnatal bone marrow and thymus, which is not something a coexpression analysis in AML transcriptomes would surface. Selleri L et al. 2004
- E5strong confidence 4 of 5: Replicated in peer-reviewed work by more than one group.paper
In mice, Pbx2-null animals are born at expected Mendelian frequencies with no detectable developmental abnormality, no reduction in long-term survival and no measurable effect on steady-state haematopoiesis or immune function; nevertheless Pbx2 is the predominant high-molecular-weight-isoform Pbx protein detectable by immunoblot in postnatal bone marrow and thymus.
The TALE homeodomain protein Pbx2 is not essential for development and long-term survival. · Selleri L, DiMartino J, van Deursen J, et al., Cleary ML · Mol Cell Biol 2004What this evidence cannot show
Murine, germline, and steady-state. Read as abstract, not full text. The authors attribute the absent phenotype to redundancy with low-molecular-weight Pbx isoforms, so this is evidence of compensation rather than of irrelevance, and a germline knockout says nothing about a requirement in a transformed cell. No stress haematopoiesis or leukaemia challenge is reported in the abstract. New to this graph - not previously cited here.
Evidence that argues against this (1)
- A gene dispensable at steady state can be required under oncogenic stress, and this graph has the worked example: PSIP1/LEDGF is dispensable in normal haematopoiesis and required in the leukaemic cell. A normal knockout phenotype is not an argument that PBX2 is irrelevant to KMT2A-rearranged disease; it is an argument that any requirement would be leukaemia-specific. Oncofusion knowledge graph, mechanism-psip1-required-in-the-leukaemic-cell-not-the-normal-one 2026
- E6established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database
PBX2 is UniProt P40425, 430 aa, primary gene name PBX2, sole gene synonym G17, recommended name Pre-B-cell leukemia transcription factor 2; PBX1 (P40424) is also exactly 430 aa and PBX3 (P40426) is 434 aa, so sequence length cannot discriminate PBX1 from PBX2 at all.
UniProtKB entries P40424 (PBX1_HUMAN), P40425 (PBX2_HUMAN) and P40426 (PBX3_HUMAN) · UniProtKB/Swiss-Prot 2026What this evidence cannot show
Resolved on 2026-09-21 with gene_exact:PBX2 AND organism_id:9606 AND reviewed:true, fields accession,id,gene_primary,gene_synonym,protein_name,length; exactly one reviewed record returned and the primary gene name was read back, then the three lengths were confirmed in a single accession query. gene_exact matches synonyms, which is why the primary-name read-back is the operative check.
Evidence that argues against this (1)
- Asserting an accession and a length is a defence against a swap and nothing more. It does not establish that PBX2 protein is present in KMT2A-rearranged blasts, which isoform is present, or that the protein does anything in this disease - and here the length half of that defence is worthless, because PBX1 and PBX2 are identical in length. Li Z et al. 2013
- E7moderate confidence 3 of 5: One strong study, or several smaller consistent ones.paper
In myeloid cells HOXA9, MEIS1 and PBX2 are all strongly expressed in the nucleus, with a portion of their signals colocalised within nuclear speckles; the same cells yield HOXA9/PBX2/MEIS1 trimeric EMSA complexes and co-immunoprecipitation of PBX2 and MEIS1 with HOXA9 from nuclear extracts.
HOXA9 forms triple complexes with PBX2 and MEIS1 in myeloid cells. · Mol Cell Biol 1999What this evidence cannot show
ABSTRACT-LEVEL ONLY - the Europe PMC fullTextXML route returned HTTP 500 and the PMC HTML route a stub on 2026-09-21, so the cell line, the antibody, the speckle marker used and any quantitation are not recoverable. A portion of their signals is the paper's own hedge and is not a statement that PBX2 is a speckle-resident protein. One paper from 1999, never replicated for PBX2. No KMT2A fusion anywhere in it.
Evidence that argues against this (1)
- The Human Protein Atlas Blood Atlas records PBX2 RNA as Not detected in immune cells with distribution Not detected, which sits directly against strong nuclear PBX2 protein in myeloid cells. Different register (RNA in sorted normal blood cells versus protein in transformed myeloid cells), but unreconciled. Human Protein Atlas 2026
- E8moderate confidence 3 of 5: One strong study, or several smaller consistent ones.database
UniProt P40425 asserts PBX2's nuclear location on ECO:0000305 (curator inference) with no experimental citation, while HPA immunofluorescence gives main location Nucleoplasm with reliability Supported.
UniProtKB P40425 (PBX2_HUMAN) SUBCELLULAR LOCATION comment, fetched 2026-09-21 · UniProt Consortium 2026What this evidence cannot show
An ECO:0000305 location is a curator's inference, not a measurement - the same grade Q71 flagged on SMARCD2. Anyone filtering UniProt on ECO:0000269 would drop PBX2's only location line entirely and record the protein as unlocalised, which would be wrong in the other direction.
Evidence that argues against this (1)
- The ECO:0000305 grade impugns the RECORD, not the fact, and it would be an error to downgrade PBX2's nuclear localisation because of it. An entirely independent measurement - antibody immunofluorescence in HPA's panel - returns Nucleoplasm as the single main location at 'Supported' reliability, and a 1999 primary paper reports strong nuclear PBX2 protein in myeloid cells. Three sources of different kinds agree; only UniProt's provenance is thin. The same HPA record is simultaneously the source of this entry's unreconciled Blood Atlas contradiction, so it is being cited here for the arm that supports and elsewhere for the arm that conflicts. Human Protein Atlas 2026
co-purifies with tagged AFF4 in BioPlex 2.0 and 3.0 (HEK293T, anti-tag co-IP, spoke-expanded); not a measured binary contact
PBC-class paralogue; P40425 and P40426, and PBX2 is exactly the length of PBX1 so verify-accessions cannot separate them
- related to →HOXA9 — required for survival of established MLL-rearranged leukemia, and dispensable for starting it
explicitly excluded as a HOXA9 co-expressed cofactor in MLL-rearranged AML by the paper that established PBX3
the hexapeptide groove HXR9 disrupts is shared across PBX1/2/3, so a PBX3-framed rationale understates the on-target normal-marrow exposure
third PBC-class member of the HOX-PBX dimer, previously unwritten in this graph
nuclear by ECO:0000305 curator inference only
the hypothesis is not expressible without a PBX2 entry; gene-pbx3 recorded PBX2 as unresolved
Part A measures PBX2 protein in KMT2A::AFF1 cells for the first time in this disease
one of the two partners with a nuclear call, and the call is curator inference
- related to →Nuclear speckles — the compartment everyone assumes KMT2A::AFF1 uses, on evidence that skips AFF1 itself
partial nuclear-speckle colocalisation with HOXA9 and MEIS1 in myeloid cells (PMID 10082572); NOT a KMT2A-fusion cell
HOXA9/PBX2/MEIS1 trimeric complex from myeloid nuclear extracts, EMSA and co-IP (PMID 10082572)
MEIS1 enhances HOXA9-PBX2 complex formation and joins the trimer (PMID 10082572)
- expressed in →Granulocyte-monocyte progenitor (GMP) — the committed cell an MLL fusion can turn back into a stem cell
strong nuclear PBX2 protein in myeloid cells (PMID 10082572); contradicted at RNA level by HPA Blood Atlas 'not detected in immune cells'