One domain, two names - and `MLL[tiab]` does not match `MLL1`. Two token traps, two missing affinity papers each
also called MT domain retrieval trap · BCB domain naming collision · why the graph held both numbers and never compared them
The same piece of the fusion protein has two names in the literature. Searching for one name finds twenty-one papers; the paper with the disagreeing number is not among them, because it uses the other name. That is why this project held both numbers for forty-five cycles without ever putting them side by side.
The same thing, for a scientist
The KMT2A region 1147-1244 is called the CXXC domain in the structural literature (Allen, Cierpicki, Risner, Xu) and the MT (methyltransferase-homology) or BCB (basic-cysteine-basic) domain in the functional literature founded by Birke 2002. Measured live on 2026-09-21: `MLL[tiab] AND CXXC[tiab]` returns 21 records; `"MT domain"[tiab] AND MLL[tiab]` returns exactly 1, which is Birke 2002; the intersection is EMPTY. Birke's own abstract never contains the string CXXC, so no CXXC query can reach the paper carrying the 33 nM SPR number. Erfurth 2008, which reconciled the two numbers in print and gives the 1147-1244 boundary, is also absent from the 21. This is a rule-70-class failure - one referent, several strings - and it is the mechanical reason this graph could cite both numbers in five and six entries respectively and never notice they disagree. Proposed as a row in data/symbol-collisions.json.
The measurement
Run at the coordinator's own tooling on 2026-09-21, one tag per term per rule 94, querytranslation recorded 1:
| query | translation | records | contains Birke 2002? |
|---|---|---|---|
MLL[tiab] AND CXXC[tiab] | "MLL"[Title/Abstract] AND "CXXC"[Title/Abstract] | 21 | no |
"MT domain"[tiab] AND MLL[tiab] | "MT domain"[Title/Abstract] AND "MLL"[Title/Abstract] | 1 | yes - it is the only record |
CXXC[tiab] AND 11842107[uid] | "CXXC"[Title/Abstract] AND 11842107[UID] | 0 | spike test: Birke is NOT indexed as CXXC in title or abstract |
"BCB domain"[tiab] | "BCB domain"[tiab] | 0 | the alternative name is unused in titles and abstracts |
KMT2A[tiab] AND CXXC[tiab] | "KMT2A"[Title/Abstract] AND "CXXC"[Title/Abstract] | 8 | no |
The 21 records reachable through MLL AND CXXC are, by PMID: 40769927, 39877387, 36598580, 35978680, 32997997, 32519403, 30352306, 29276034, 24449215, 23990460, 23697932, 21155757, 20541477, 20010842, 19060922, 16990798, 16897742, 15547684, 15542854, 15375572, 12124344.
Two of the five papers that carry an affinity measurement for this domain are missing from that list: Birke 2002 (PMID 11842107, the 33 nM SPR) and Erfurth 2008 (PMID 18483194, the five-point ITC ladder and the published reconciliation of the discrepancy). Both are missing for the same reason - their abstracts frame the work as methylation protection and use MT domain, never CXXC.
Note also that two of the 21 are noise from the CXXCn ordinal collision already in the registry: 15547684 and 15375572 are in silico gene-identification papers about FBXL19 and 'CXXC10'.
The second trap, found by being caught by it: MLL does not match MLL1
This beat ran the queries above, concluded that 21 records was the reachable CXXC literature, and missed a sixth affinity paper that was already inside one of the entries it had been sent to correct.
PMID 34280370 - Liang et al., Biophysical Journal 2021, Dynamics and inhibition of MLL1 CXXC domain on DNA revealed by single-molecule quantification - carries Kd 5.7 +/- 0.2 uM at 150 mM NaCl for a tagless CXXC domain, which is the single most physiologically apt measurement of this contact in the literature. Measured 2026-09-21 3:
| query | translation | records | contains Liang 2021? |
|---|---|---|---|
MLL[tiab] AND CXXC[tiab] | both [Title/Abstract] | 21 | no |
MLL1[tiab] AND CXXC[tiab] | both [Title/Abstract] | 8 | yes |
MLL[tiab] AND CXXC[tiab] AND 34280370[uid] | spike test | 0 | confirms the token does not match |
MLL1[tiab] AND CXXC[tiab] AND 34280370[uid] | spike test | 1 | confirms it does under MLL1 |
PubMed [tiab] matches whole tokens. MLL and MLL1 are different tokens, and the field uses both interchangeably for the same protein: Cierpicki's title says MLL CXXC, Liang's says MLL1 CXXC. Neither query reaches the other's paper unless both strings are run.
So the reachable literature for this domain needs at least four strings: MLL, MLL1, KMT2A and "MT domain". Three of them were run by this beat and the fourth was not, which cost a paper that changes the beat's own central number.
The registry already warns about MLL as a free-text token - ten of twenty-six records in one query were microbiology and wastewater papers - and the fix it prescribes, always query KMT2A, or MLL with a disease term, would not have helped here: KMT2A[tiab] AND CXXC[tiab] returns 8 and does not include Liang either, because the paper is from 2021 and still says MLL1. The existing row addresses precision and this is a recall failure on the same token.
How it was actually found: by reading the counter-evidence array of exp-cxxc-reader-depletion-versus-kmt2a-fusion-occupancy, one of the six entries this beat was sent to amend. The graph already held the paper that corrected the beat's own analysis, in the entry the beat was correcting. That is the second time in two cycles - cycle 45's Kerry finding had the same shape.
Why this is the mechanism of the failure, not a side note
This graph cited PMID 20010842 in six entries and PMID 11842107 in five, and the two sets are disjoint - no entry cited both. That is exactly what you would expect if the two papers were found by different queries on different beats and never co-retrieved. The structural beats searched CXXC and found Cierpicki, Allen, Risner and Xu; the methylome beat searched methylation and CpG and found Birke. The graph's own citation pattern is a shadow of the retrieval split.
The brief's rule 70 says a counted absence about a noncoding element is bounded by its name list. This is the coding-domain twin, and it is worse in one respect: a gene has HGNC, so SEPT9/SEPTIN9 is resolvable by lookup. A protein domain has no naming authority at all. Pfam calls this one zf-CXXC (PF02008), UniProt calls it a CXXC-type zinc finger with boundaries 1147-1195, the 2002 literature calls it MT or BCB with boundaries 1147-1244, and the structures call it CXXC with boundaries 1147-1203. Four names, four boundaries, no authority.
What to do, generalised: before recording any domain-level absence or comparing any two domain-level measurements, enumerate the domain's names from the full text of the founding paper - not from the current structural literature, which has usually renamed it - and run each name as a separate query. Then check whether the name sets intersect. If they do not, you have two literatures and you have read one.
Proposed registry row (rule 88 - I do not edit data/symbol-collisions.json)
Grepped data/symbol-collisions.json (87 rows) for MLL, CXXC and CpG before any query, as rule 88 requires. Three relevant rows exist - MLL as a free-text token, CXXCn as gene symbol versus ordinal domain reference, and MLL2/MLL4 - and none covers this. Proposed new row:
{
"token": "MT domain / BCB domain (KMT2A 1147-1244)",
"class": "one_protein_domain_two_names_two_disjoint_literatures",
"this_graph_means": "the CpG-binding region of KMT2A; the MT/BCB name covers 1147-1244, the CXXC name usually covers 1147-1203",
"measured": {
"MLL[tiab] AND CXXC[tiab]": 21,
"\"MT domain\"[tiab] AND MLL[tiab]": 1,
"intersection": 0,
"CXXC[tiab] AND 11842107[uid]": 0,
"\"BCB domain\"[tiab]": 0,
"date": "2026-09-21",
"tool": "PubMed E-utilities esearch, one tag per term"
},
"why_it_matters": "The only SPR affinity for this domain (PMID 11842107, 33 nM) and the only multi-oligonucleotide ITC ladder plus the published reconciliation of the 1300-fold discrepancy (PMID 18483194) are BOTH unreachable from any CXXC query. This graph cited the two literatures in disjoint entry sets for 45 cycles.",
"block_autogeneration": false,
"found_by": "Q82-cxxc-affinity"
}
| proposed registry row | see the third section; proposed only - data/symbol-collisions.json is not edited by beats (rule 88) SECOND PROPOSED ROW, or an amendment to the existing MLL row: `MLL[tiab]` does not match the token `MLL1`. The existing registry row for MLL is about PRECISION (a three-letter token matching unrelated fields) and prescribes querying KMT2A instead. That prescription does not fix the RECALL failure measured here, because KMT2A[tiab] AND CXXC[tiab] also returns 8 and also misses PMID 34280370. Any KMT2A-domain query must run MLL, MLL1 and KMT2A as three separate strings. |
|---|
queries — the numbers behind the chart
[
{
"query": "MLL[tiab] AND CXXC[tiab]",
"querytranslation": "\"MLL\"[Title/Abstract] AND \"CXXC\"[Title/Abstract]",
"records": 21,
"date": "2026-09-21",
"tool": "PubMed esearch"
},
{
"query": "\"MT domain\"[tiab] AND MLL[tiab]",
"querytranslation": "\"MT domain\"[Title/Abstract] AND \"MLL\"[Title/Abstract]",
"records": 1,
"date": "2026-09-21",
"tool": "PubMed esearch"
},
{
"query": "KMT2A[tiab] AND CXXC[tiab]",
"querytranslation": "\"KMT2A\"[Title/Abstract] AND \"CXXC\"[Title/Abstract]",
"records": 8,
"date": "2026-09-21",
"tool": "PubMed esearch"
},
{
"query": "CXXC[tiab] AND 11842107[uid]",
"querytranslation": "\"CXXC\"[Title/Abstract] AND 11842107[UID]",
"records": 0,
"date": "2026-09-21",
"tool": "PubMed esearch",
"role": "spike test"
},
{
"query": "\"BCB domain\"[tiab]",
"querytranslation": "\"BCB domain\"[tiab]",
"records": 0,
"date": "2026-09-21",
"tool": "PubMed esearch"
},
{
"query": "CXXC[tiab] AND \"surface plasmon resonance\"[tiab]",
"querytranslation": "\"CXXC\"[Title/Abstract] AND \"surface plasmon resonance\"[Title/Abstract]",
"records": 6,
"date": "2026-09-21",
"tool": "PubMed esearch",
"role": "positive control through the identical shape"
},
{
"query": "CXXC[tiab] AND \"isothermal titration calorimetry\"[tiab]",
"querytranslation": "\"CXXC\"[Title/Abstract] AND \"isothermal titration calorimetry\"[Title/Abstract]",
"records": 5,
"date": "2026-09-21",
"tool": "PubMed esearch",
"role": "positive control through the identical shape"
},
{
"query": "MLL1[tiab] AND CXXC[tiab]",
"querytranslation": "\"MLL1\"[Title/Abstract] AND \"CXXC\"[Title/Abstract]",
"records": 8,
"date": "2026-09-21",
"tool": "PubMed esearch"
},
{
"query": "MLL[tiab] AND CXXC[tiab] AND 34280370[uid]",
"querytranslation": "\"MLL\"[Title/Abstract] AND \"CXXC\"[Title/Abstract] AND 34280370[UID]",
"records": 0,
"date": "2026-09-21",
"tool": "PubMed esearch",
"role": "spike test - MLL does not match MLL1"
},
{
"query": "MLL1[tiab] AND CXXC[tiab] AND 34280370[uid]",
"querytranslation": "\"MLL1\"[Title/Abstract] AND \"CXXC\"[Title/Abstract] AND 34280370[UID]",
"records": 1,
"date": "2026-09-21",
"tool": "PubMed esearch",
"role": "spike test - MLL1 does"
}
]mll and cxxc pmids
[ "40769927", "39877387", "36598580", "35978680", "32997997", "32519403", "30352306", "29276034", "24449215", "23990460", "23697932", "21155757", "20541477", "20010842", "19060922", "16990798", "16897742", "15547684", "15375572", "15542854", "12124344" ]
missing affinity papers
[
{
"pmid": "11842107",
"why_missing": "abstract says MT domain, never CXXC",
"what_it_carries": "the 33 nM SPR measurement"
},
{
"pmid": "18483194",
"why_missing": "abstract frames the work as CpG protection at Hoxa9",
"what_it_carries": "the five-point ITC ladder, the 1147-1244 boundary, and the 2008 reconciliation of the discrepancy"
},
{
"pmid": "34280370",
"why_missing": "title and abstract say MLL1, and MLL[tiab] does not match the token MLL1",
"what_it_carries": "Kd 5.7 uM at 150 mM NaCl for a tagless CXXC domain - the most physiologically apt measurement in the literature - plus a single-molecule landscape on a real Hoxa9 CpG island and a dimethyl fumarate IC50 of 0.91 uM"
}
]graph citation split before this cycle — the numbers behind the chart
{
"pmid_20010842_entries": 6,
"pmid_11842107_entries": 5,
"entries_citing_both": 0,
"pmid_18483194_entries": 0
}domain naming authorities
{
"Pfam": "zf-CXXC, PF02008",
"InterPro": "IPR002857",
"UniProt_Q03164": "Zinc finger, CXXC-type, 1147-1195",
"structural_literature": "CXXC domain, 1147-1203",
"Birke_2002_and_Erfurth_2008": "MT domain / BCB domain, 1147-1244",
"note": "four names, four boundaries, no naming authority for protein domains equivalent to HGNC for genes"
}strings needed to reach this literature
[ "MLL", "MLL1", "KMT2A", "\"MT domain\"", "and note that \"BCB domain\" returns 0 and reaches nothing" ]
- If two literatures about one domain do not intersect, a drug programme reading only the structural half will design against 1147-1203 and miss that the functional half has always worked with 1147-1244 - which is exactly the construct difference at the heart of the affinity discrepancy.
- This beat was itself caught by the trap it is documenting, and found the missing paper only by reading an entry it was correcting. Any bounded absence written by token enumeration in this project should be assumed to have the same exposure until a forward-citation walk has been run alongside it.
- How many other entries in this graph rest on a literature enumeration that ran MLL but not MLL1? A corpus sweep of recorded query strings for MLL[tiab] without a sibling MLL1[tiab] would size it in one command.
- How many other domain-level comparisons in this graph are split across two names? A sweep of domain aliases against the corpus's citation sets would find them, and nothing like it has been run.
- Would routing domain-level queries through Europe PMC full-text search by default have caught this? It is one line of tooling change and would be worth measuring on a known-positive set.
- The CXXCn registry row warns that CXXC2 is KDM2B and CXXC8 is KDM2A. KMT2A's own alias list includes CXXC7. Does any entry in this graph use CXXC7 where it means KMT2A, or vice versa?
- E1established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database
As of 2026-09-21, MLL[tiab] AND CXXC[tiab] returns 21 PubMed records and PMID 11842107 is not among them; "MT domain"[tiab] AND MLL[tiab] returns exactly one record, which is PMID 11842107; CXXC[tiab] AND 11842107[uid] returns 0, confirming the paper carries no CXXC token in its title or abstract; and "BCB domain"[tiab] returns 0.
PubMed E-utilities esearch, live queries with querytranslation recorded · NCBI Entrez 2026What this evidence cannot show
Counts are of a single index on a single day and PubMed counts drift. Every query is written one tag per term per rule 94 and the querytranslation string was read back for each; none shows an [All Fields] fallback or a MeSH expansion. The operand controls ran clean through the identical shape: CXXC[tiab] AND "surface plasmon resonance"[tiab] returns 6 and CXXC[tiab] AND "isothermal titration calorimetry"[tiab] returns 5, so the instrument can return a one. The 21-record list is title-checked only to the extent of noting two in-silico CXXCn papers as off-topic.
Evidence that argues against this (1)
- Retrieval is not the whole explanation. Three entries written in cycle 45 DID hold both numbers side by side in their caveats and flagged the discrepancy explicitly, so once the methylome beat cited Birke the collision became visible without any query being run. The retrieval split explains why it took 45 cycles, not why it was never noticed at all. Birke M et al. 2002
- E2established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.paper
Birke et al. name the domain MT (methyltransferase-homology) and give BCB (basic-cysteine-basic) as an explicit alternative name, and their abstract describes the work as CpG binding and methylation discrimination without using the string CXXC.
The MT domain of the proto-oncoprotein MLL binds to CpG-containing DNA and discriminates against methylation. · Birke M, Schreiner S, García-Cuéllar MP, et al. · Nucleic Acids Res 2002What this evidence cannot show
The paper's Discussion does use CxxC when relating the domain to DNMT1, MBD1 and CGBP, so the token is present in the full text; it is the abstract and title that lack it, which is what determines PubMed retrieval (rule 80). Full text read via the PMC HTML route.
Evidence that argues against this (1)
- Europe PMC full-text search would reach the paper on CxxC where esearch does not, so this is a limitation of the abstract index rather than of all retrieval. A beat using full-text search from the start would not have hit this - which is an argument for making full-text search the default for domain-level questions rather than an argument about naming. Erfurth FE et al. 2008
- E3established confidence 5 of 5: Multiple independent lines of evidence; treated as settled in the field.database
PubMed [tiab] matches whole tokens, so MLL[tiab] does not match MLL1: MLL[tiab] AND CXXC[tiab] returns 21 records and excludes PMID 34280370, while MLL1[tiab] AND CXXC[tiab] returns 8 and includes it, and KMT2A[tiab] AND CXXC[tiab] returns 8 and also excludes it.
PubMed E-utilities esearch, live queries with querytranslation recorded and UID spike tests · NCBI Entrez 2026What this evidence cannot show
Counts from one index on 2026-09-21. Both spike tests were run - MLL[tiab] AND CXXC[tiab] AND 34280370[uid] returns 0 and MLL1[tiab] AND CXXC[tiab] AND 34280370[uid] returns 1 - so this is a demonstrated token-matching behaviour and not an inference from a count. The union of MLL, MLL1, KMT2A and "MT domain" queries has not been deduplicated and counted here; the individual counts are 21, 8, 8 and 1.
Evidence that argues against this (1)
- The same failure would be avoided entirely by Europe PMC full-text search or by simply following the citation graph - Liang 2021 cites Cierpicki 2010 and Erfurth 2008 directly, so a forward-citation walk from either would have found it on the first hop. Token enumeration is the fragile route and a citation walk is the robust one; this beat used neither until it read its own corpus. Liang L et al. 2021
The reason the two ends of the ladder were never compared: Birke 2002 is unreachable from any CXXC query and Erfurth 2008 was cited nowhere in this graph.
- related to →KMT2A / MLL1 — the gene that breaks
The KMT2A region 1147-1244 carries two names with disjoint literatures.
The same retrieval failure is why a method-level absence cannot be written as a counted query in this literature.
The MT/BCB name is attached to the longer construct and the CXXC name to the shorter one, so the naming split and the construct split are the same split.