A phase I dose-escalation study of aflibercept administered in combination with pemetrexed and cisplatin in patients with advanced solid tumours
Bibliographic record
Abstract
BACKGROUND: To evaluate the safety, pharmacokinetics (PKs), and pharmacodynamics of aflibercept, and to identify the recommended phase II dose (RP2D) of aflibercept in combination with pemetrexed and cisplatin. METHODS: Aflibercept was administered at escalating doses of 2, 4, or 6 mg kg(-1) in combination with fixed doses of pemetrexed (500 mg m(-2)) plus cisplatin (75 mg m(-2)) every 3 weeks. Blood samples were collected for PK analyses. Serum antiaflibercept antibodies were quantified to assess their impact on systemic aflibercept concentrations. RESULTS: Eighteen patients were enrolled. One patient dosed at 4 mg kg(-1) experienced grade 3 hypophosphatemia (dose-limiting toxicity; DLT), which prompted a cohort expansion. No further DLTs were observed in the 4 mg kg(-1) cohort or the 6 mg kg(-1) dose cohort. Most common adverse events (AEs) of all grades included (%): fatigue (89), anaemia (89), nausea (83), hyponatremia (78), and neutropenia (72). Grade ≥ 3 AEs consistent with anti-vascular endothelial growth factor therapy included (%): hypertension (22), pulmonary embolism (11), and deep vein thrombosis (6). Five patients (28%) experienced mild neurocognitive disturbance. No episodes of reversible posterior leukoencephalopathy syndrome (RPLS) were noted. CONCLUSION: The results of this phase I study allowed further evaluation of the combination of aflibercept with pemetrexed and cisplatin in a phase II study. The RP2D of aflibercept was 6 mg kg(-1), to be administered intravenously every 3 weeks in combination with pemetrexed and cisplatin.
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.001 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.002 | 0.001 |
| Bibliometrics | 0.000 | 0.001 |
| Science and technology studies | 0.000 | 0.001 |
| Scholarly communication | 0.001 | 0.001 |
| Open science | 0.001 | 0.000 |
| Research integrity | 0.001 | 0.004 |
| Insufficient payload (model declined to judge) | 0.002 | 0.001 |
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".