Characterising the biology of novel lytic bacteriophages infecting multidrug resistant Klebsiella pneumoniae
Bibliographic record
Abstract
BACKGROUND: Members of the genus Klebsiella are among the leading microbial pathogens associated with nosocomial infection. The increased incidence of antimicrobial resistance in these species has propelled the need for alternate/combination therapeutic regimens to aid clinical treatment. Bacteriophage therapy forms one of these alternate strategies. METHODS: Electron microscopy, burst size, host range, sensitivity of phage particles to temperature, chloroform, pH, and restriction digestion of phage DNA were used to characterize Klebsiella phages. RESULTS AND CONCLUSIONS: Of the 32 isolated phages eight belonged to the family Myoviridae, eight to the Siphoviridae whilst the remaining 16 belonged to the Podoviridae. The host range of these phages was characterised against 254 clinical Enterobacteriaceae strains including multidrug resistant Klebsiella isolates producing extended-spectrum beta-lactamases (ESBLs). Based on their lytic potential, six of the phages were further characterised for burst size, physicochemical properties and sensitivity to restriction endonuclease digestion. In addition, five were fully sequenced. Multiple phage-encoded host resistance mechanisms were identified. The Siphoviridae phage genomes (KP16 and KP36) contained low numbers of host restriction sites similar to the strategy found in T7-like phages (KP32). In addition, phage KP36 encoded its own DNA adenine methyltransferase. The φKMV-like KP34 phage was sensitive to all endonucleases used in this study. Dam methylation of KP34 DNA was detected although this was in the absence of an identifiable phage encoded methyltransferase. The Myoviridae phages KP15 and KP27 both carried Dam and Dcm methyltransferase genes and other anti-restriction mechanisms elucidated in previous studies. No other anti-restriction mechanisms were found, e.g. atypical nucleotides (hmC or glucosyl hmC), although Myoviridae phage KP27 encodes an unknown anti-restriction mechanism that needs further investigation.
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.001 | 0.000 |
| Science and technology studies | 0.000 | 0.000 |
| Scholarly communication | 0.001 | 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".