Different mechanisms of two anti-anthrax protective antigen antibodies and function comparison between them
Bibliographic record
Abstract
BACKGROUND: Bacillus anthracis causes a highly lethal infectious disease primarily due to toxin-mediated injury. Antibiotics are no longer effective to treat the accumulation of anthrax toxin, thereby new strategies of antibody treatment are essential. Two anti- anthrax protective antigen (PA) antibodies, hmPA6 and PA21, have been reported by our lab previously. METHODS: The mechanisms of the two antibodies were elucidated by Electrophoresis, Competitive Enzyme-linked immune sorbent assay, Western blot analysis and immunoprecipitation test, and in vitro, in vivo (F344 rats) treatment test. The epitopes of the two antibodies were proved by Western blot and Enzyme-linked immune sorbent assay with different domains of PA. RESULTS: In this study, we compared affinity and neutralization of these two antibodies. PA21 was better in protecting cells and rats, whereas hmPA6 had higher affinity. Furthermore, the neutralization mechanisms of the two antibodies and their recognition domains of PA were studied. The results showed that hmPA6 recognized domain IV, thus PA could not bind to cell receptors. Conversely, PA21 recognized domain II, thereby limiting heptamer oligomerization of PA63 in cells. CONCLUSIONS: Our studies elucidated the mechanisms and epitopes of hmPA6 and PA21. The present investigation can advance future use of the two antibodies in anthrax treatment or prophylaxis, and potentially as a combination treatment as the antibodies target different epitopes.
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.000 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.000 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.000 | 0.000 |
| Open science | 0.000 | 0.000 |
| Research integrity | 0.001 | 0.001 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".