Interaction of a Bacterially Expressed Peptide from the Receptor Binding Domain of <i>Pseudomonas aeruginosa</i> Pili Strain PAK with a Cross-Reactive Antibody: Conformation of the Bound Peptide
Bibliographic record
Abstract
The C-terminal receptor binding region of Pseudomonas aeruginosa pilin protein strain PAK (residues 128-144) has been the target for the design of a vaccine effective against P. aeruginosa infections. We have recently cloned and expressed a (15)N-labeled PAK pilin peptide spanning residues 128-144 of the PAK pilin protein. The peptide exists as a major (trans) and minor (cis) species in solution, arising from isomerization around a central Ile(138)-Pro(139) peptide bond. The trans isomer adopts two well-defined turns in solution, a type I beta-turn spanning Asp(134)-Glu-Gln-Phe(137) and a type II beta-turn spanning Pro(139)-Lys-Gly-Cys(142). The cis isomer adopts only one well-defined type II beta-turn spanning Pro(139)-Lys-Gly-Cys(142) but displays evidence of a less ordered turn spanning Asp(132)-Gln-Asp-Glu(135). These turns have been implicated in cross-reactive antibody recognition. (15)N-edited NMR spectroscopy was used to study the binding of the (15)N-labeled PAK pilin peptide to an Fab fragment of a cross-reactive monoclonal antibody, PAK-13, raised against the intact PAK pilus. The results of these studies are as follows: the trans and cis isomers bind with similar affinity to the Fab, despite their different topologies; both isomers maintain the conformational integrity of their beta-turns when bound; binding leads to the preferential stabilization of the first turn over the second turn in each isomer; and binding leads to the perturbation of resonances within regions of the trans and cis backbone that undergo microsecond to millisecond motions. These slow motions may play a role in induced fit binding of the first turn to Fab PAK-13, which would allow the same antibody combining site to accommodate either trans or cis topology. More importantly for vaccine design, these motions may also play a role in the development of a broad-spectrum vaccine capable of generating an antibody therapeutic effective against the multiple strains of P. aeruginosa.
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.000 | 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.000 | 0.000 |
| 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".