Quantum mechanical study of the β- and δ-lyase reactions during the base excision repair process: application to FPG
Bibliographic record
Abstract
Bacterial FPG (or MutM) is a bifunctional DNA glycosylase that is primarily responsible for excising 8-oxoguanine (OG) from the genome by cleaving the glycosidic bond and the DNA backbone at the 3'- and 5'-phosphates of the damaged nucleoside. In the present work, quantum mechanical methods (SMD-M06-2X/6-311+G(2df,2p)//IEF-PCM-B3LYP/6-31G(d)) and a ring-opened Schiff base model that includes both the 3'- and 5'-phosphate groups are used to investigate the β- and δ-elimination reactions facilitated by FPG. Both the β- and δ-elimination reactions are shown to proceed through an E1cB mechanism that involves proton abstraction prior to the phosphate-ribose bond cleavage. Since transition states for the phosphate elimination reactions could not be characterized in the absence of leaving group protonation, our work confirms that the phosphate elimination reactions require protonation by a residue in the FPG active site, and can likely be further activated by additional active-site interactions. Furthermore, our model suggests that 5'-PO4 activation may proceed through a nearly isoenergetic direct (intramolecular) proton transfer involving the O4' proton of the deoxyribose of the damaged nucleoside. Regardless, our model predicts that both 3'- and 5'-phosphate protonation and elimination steps occur in a concerted reaction. Most importantly, our calculated barriers for the phosphate cleavage reactions reveal inherent differences between the β- and δ-elimination steps. Indeed, our calculations provide a plausible explanation for why the δ-elimination rather than the β-elimination is the rate-determining step in the BER facilitated by FPG, and why some bifunctional glycosylases (including the human counterpart, hOgg1) lack δ-lyase activity. Together, the new mechanistic features revealed by our work can be used in future large-scale modeling of the DNA-protein system to unveil the roles of key active sites residues in these relatively unexplored BER steps.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.000 | 0.001 |
| Meta-epidemiology (narrow) | 0.000 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.000 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.000 | 0.001 |
| Insufficient payload (model declined to judge) | 0.001 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".