Bibliographic record
Abstract
No AccessJournal of UrologyCLINICAL UROLOGY: Letters to the Editor1 Jan 2003RE: DOES PC-SPES INTERACT WITH WARFARIN? Graeme G. Duncan Graeme G. DuncanGraeme G. Duncan More articles by this author View All Author Informationhttps://doi.org/10.1016/S0022-5347(05)64108-0AboutFull TextPDF ToolsAdd to favoritesDownload CitationsTrack CitationsPermissionsReprints ShareFacebookLinked InTwitterEmail "RE: DOES PC-SPES INTERACT WITH WARFARIN?." The Journal of Urology, 169(1), pp. 294–295 References 1 : Disseminated intravascular coagulation and PC-SPES: a case report and literature review. Can J Urol2001; 8: 1326. Google Scholar 2 : Fever, cancer incidence and spontaneous remissions. Neuroimmunomodulation2001; 9: 55. Google Scholar 3 : Disseminated intravascular coagulation and excessive fibrinolysis in a patient with metastatic prostate cancer. Response to epsilon-aminocaproic acid. Cancer1992; 70: 656. Google Scholar 4 : http://www.hc-sc.gc.ca/english/protection/warnings/2002/2002_06e.htm. Google Scholar 5 : Health Canada Online. http://www.hc-sc.gc.ca/english/protection/warnings/2002/2002_06e.htm. Google Scholar 6 Small, E.J., Kantoff, P., Weinberg, W.K., Nguyen, S., Smith, M., Bubley, G.J. et-al: A prospective multicenter randomized trial of the herbal supplement, PC-SPES vs. diethylstilbestrol (DES) in patients with advanced, androgen independent prostate cancer (AiPCa). Presented at annual meeting of American Society of Clinical Oncology, Orlando, Florida, May 18–21, 2002. Google Scholar 7 : Pulmonary embolus related to PC-SPES use in a patient with PSA recurrence after radical prostatectomy. Urology2002; 59: 444. Google Scholar Department of Radiation Oncology, BC Cancer Agency, 600 W. 10th Ave., Vancouver, British Columbia, Canada V5Z 4E6© 2003 by American Urological Association, Inc.FiguresReferencesRelatedDetails Volume 169Issue 1January 2003Page: 294-295 Advertisement Copyright & Permissions© 2003 by American Urological Association, Inc.MetricsAuthor Information Graeme G. Duncan More articles by this author Expand All Advertisement PDF DownloadLoading ...
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.002 | 0.014 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.001 |
| Bibliometrics | 0.001 | 0.001 |
| Science and technology studies | 0.001 | 0.001 |
| Scholarly communication | 0.003 | 0.003 |
| Open science | 0.002 | 0.001 |
| Research integrity | 0.010 | 0.006 |
| Insufficient payload (model declined to judge) | 0.046 | 0.025 |
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".