HNRNPA2B1 review notes

Why this gene was selected

Two standing claims about HNRNPA2B1 sit outside its uncontested hnRNP biology: that it is a nuclear
"reader" of the m6A RNA modification, and that it is a nuclear DNA sensor initiating innate immune
signalling. A 2026 RNA Biology paper attacks the first. The question for curation was what GOA
actually carries for each.

First: what does GOA actually carry?

Checked directly in HNRNPA2B1-goa.tsv:

No 2025-26 paper independently re-tests the DNA-sensor claim. What exists builds on it rather than
testing it: PMID:41134667 (Cell Rep 2025, U1 snRNA promotes hnRNPA2B1 dimerisation —
PMID:41134667) and PMID:40689679
(mBio 2025, mtDNA sensing during SFTSV infection). Both assume the role. The 2019 paper is not
retracted and carries no notice in its PubMed record; I have marked its reference_review.correctness
as UNVERIFIED rather than VERIFIED, because I could confirm the identifier and title but not an
independent replication of the central claim.

The m6A reader question

The 2026 paper (PMID:41662154, Park et al., RNA Biol 23(1):1-28, 2026)

Verified on PubMed; DOI 10.1080/15476286.2026.2627781; full text cached. MD simulation plus
microscale thermophoresis, using the RRM1-RRM2 fusion construct from Wu et al.

PMID:41662154 and, on the mechanism,
PMID:41662154, with the bottom line
PMID:41662154 In the discussion:
PMID:41662154. The experimental leg:
PMID:41662154 (~10 nM difference,
< 0.1 kcal/mol, the methylated one slightly worse).

This is not a lone 2026 paper

Following its reference [5] led to Wu et al., Nat Commun 9:420 (2018), PMID:29379020, verified —
crystal structures of the tandem RRMs on several RNA substrates:
PMID:29379020 and the explicit conclusion
PMID:29379020 ... PMID:29379020 "reader" of m6A
modification (the quoted words in the original are typeset with curly quotes around "m6A switch" and
"reader", so the verbatim span is broken around them).

Two independent methods, eight years apart, reach the same conclusion.

What the original annotation rests on

PMID:26321680 (Alarcón et al., Cell 2015, verified) is the IDA:
PMID:26321680 and
PMID:26321680.

Note the logic: the CLIP footprint matching the m6A consensus is the evidence for reading. But the
METTL3 consensus GGAC overlaps the AGG/UAG motifs HNRNPA2B1 prefers on sequence grounds alone, so the
footprint overlap is fully explained without any methyl-specific recognition.

Position taken

GO:1990247 → MARK_AS_OVER_ANNOTATED, not REMOVE. Reasons for stopping short of removal:
1. It is an IDA and I have not read the full Alarcón text; project rules forbid removing an
experimental annotation on that basis.
2. The binding is real. HNRNPA2B1 does bind m6A-containing transcripts and does mediate m6A-dependent
effects on splicing and pri-miRNA processing. What fails is the selectivity the word "reader"
asserts, via the "m6A switch" alternative (methylation changes RNA structure, exposing the motif).
3. The 2026 measurements used an isolated RRM1-RRM2 fusion, not full-length protein with its
low-complexity domain, and a single GGACU context. Recorded as a limitation in the reference review.

The downstream process annotations are kept as ACCEPT: GO:0031053 primary miRNA processing and
GO:0000398 mRNA splicing, via spliceosome survive the demotion, because HNRNPA2B1 can recruit
Microprocessor to pri-miRNAs it binds by sequence without reading the mark. This is the point of
separating the MF from the BP.

Other curation decisions

Core functions asserted

Four, none of which depends on the m6A or DNA-sensor questions:
pre-mRNA intronic binding → splicing; A2RE 3'-UTR binding → mRNA transport/export;
LC-domain condensate scaffolding; miRNA binding → primary miRNA processing.

What I could not resolve

Whether full-length HNRNPA2B1, in a condensate, discriminates m6A. Every negative result so far comes
from isolated RRM constructs in dilute solution. And whether the 2019 DNA-sensor result replicates —
I found no independent test of it, only work that assumes it.