Faculty Opinions recommendation of Epstein-Barr virus exploits BSAP/Pax5 to achieve the B-cell specificity of its growth-transforming program.
Bibliographic record
Abstract
Epstein-Barr virus (EBV) can infect various cell types but limits its classical growth-transforming function to B lymphocytes, the cells in which it persists in vivo.Transformation initiates with the activation of Wp, a promoter present as tandemly repeated copies in the viral genome.Assays with short Wp reporter constructs have identified two promoter-activating regions, one of which (UAS2) appears to be lineage independent, while the other (UAS1) was B-cell specific and contained two putative binding sites for the B-cell-specific activator protein BSAP/Pax5.To address the physiologic relevance of these findings, we first used chromosome immunoprecipitation assays and found that BSAP is indeed bound to Wp sequences on the EBV genome in transformed cells.Thereafter, we constructed recombinant EBVs carrying two Wp copies, both wild type, with UAS1 or UAS2 deleted, or mutated in the BSAP binding sites.All the viruses delivered their genomes to the B-cell nucleus equally well.However, the BSAP binding mutant (and the virus with UAS1 deleted) showed no detectable activity in B cells, whether measured by early Wp transcription, expression of EBV latent proteins, or outgrowth of transformed cells.This was a B-cell-specific defect since, on entry into epithelial cells, an environment where Wp is not the latent promoter of choice, all the Wp mutant viruses initiated infection as efficiently as wild-type virus.We infer that EBV ensures the B-cell specificity of its growth-transforming function by exploiting BSAP/Pax5 as a lineage-specific activator of the transforming program.
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.001 | 0.002 |
| Meta-epidemiology (narrow) | 0.001 | 0.000 |
| Meta-epidemiology (broad) | 0.000 | 0.000 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.001 |
| Open science | 0.001 | 0.001 |
| Research integrity | 0.002 | 0.002 |
| Insufficient payload (model declined to judge) | 0.364 | 0.213 |
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".