Expression of PTRF in PC-3 Cells Modulates Cholesterol Dynamics and the Actin Cytoskeleton Impacting Secretion Pathways
Bibliographic record
Abstract
Expression of caveolin-1 is up-regulated in prostate cancer metastasis and is associated with aggressive recurrence of the disease. Intriguingly, caveolin-1 is also secreted from prostate cancer cell lines and has been identified in secreted prostasomes. Caveolin-1 is the major structural component of the plasma membrane invaginations called caveolae. Co-expression of the coat protein Polymerase I and transcript release factor (PTRF) is required for caveolae formation. We recently found that expression of caveolin-1 in the aggressive prostate cancer cell line PC-3 is not accompanied by PTRF, leading to noncaveolar caveolin-1 lipid rafts. Moreover, ectopic expression of PTRF in PC-3 cells sequesters caveolin-1 into caveolae. Here we quantitatively analyzed the effect of PTRF expression on the PC-3 proteome using stable isotope labeling by amino acids in culture and subcellular proteomics. We show that PTRF reduced the secretion of a subset of proteins including secreted proteases, cytokines, and growth regulatory proteins, partly via a reduction in prostasome secretion. To determine the cellular mechanism accounting for the observed reduction in secreted proteins we analyzed total membrane and the detergent-resistant membrane fractions. Our data show that PTRF expression selectively impaired the recruitment of actin cytoskeletal proteins to the detergent-resistant membrane, which correlated with altered cholesterol distribution in PC-3 cells expressing PTRF. Consistent with this, modulating cellular cholesterol altered the actin cytoskeleton and protein secretion in PC-3 cells. Intriguingly, several proteins that function in ER to Golgi trafficking were reduced by PTRF expression. Taken together, these results suggest that the noncaveolar caveolin-1 found in prostate cancer cells generates a lipid raft microenvironment that accentuates secretion pathways, possibly at the step of ER sorting/exit. Importantly, these effects could be modulated by PTRF expression.
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.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".