Ni, Pd, Pt, and Ru Complexes of Phosphine-Borate Ligands
Bibliographic record
Abstract
The species Cy(2)PHC(6)F(4)BF(C(6)F(5))(2) reacts with Pt(PPh(3))(4) to yield the new product cis-(PPh(3))(2)PtH(Cy(2)PC(6)F(4)BF(C(6)F(5))(2)) 1 via oxidative addition of the P-H bond of the phosphonium borate to Pt(0). The corresponding reaction with Pd(PPh(3))(4) affords the Pd analogue of 1, namely, cis-(PPh(3))(2)PdH(Cy(2)PC(6)F(4)BF(C(6)F(5))(2)) 3; while modification of the phosphonium borate gave the salt [(PPh(3))(3)PtH][(tBu(2)PC(6)F(4)BF(C(6)F(5))(2))] 2. Alternatively initial deprotonation of the phosphonium borate gave [tBu(3)PH][Cy(2)PC(6)F(4)BF(C(6)F(5))(2)] 4, [SIMesH][Cy(2)PC(6)F(4)BF(C(6)F(5))(2)] 5 which reacted with NiCl(2)(DME) yielding [BaseH](2)[trans-Cl(2)Ni(Cy(2)PC(6)F(4)BF(C(6)F(5))(2))(2)] (Base = tBu(3)P 6, SIMes 7) or with PdCl(2)(PhCN)(2) to give [BaseH](2)[trans-Cl(2)Pd(Cy(2)PC(6)F(4)BF(C(6)F(5))(2))(2)] (Base = tBu(3)P 8, SIMes 9). While [C(10)H(6)N(2)(Me)(4)H][tBu(2)PC(6)F(4)BF(C(6)F(5))(2)] 10 was also prepared. A third strategy for formation of a metal complex of anionic phosphine-borate derivatives was demonstrated in the reaction of (COD)PtMe(2) with the neutral phosphine-borane Mes(2)PC(6)F(4)B(C(6)F(5))(2) affording (COD)PtMe(Mes(2)PC(6)F(4)BMe(C(6)F(5))(2)) 11. Extension of this reactivity to tBu(2)PH(CH(2))(4)OB(C(6)F(5))(3)) was demonstrated in the reaction with Pt(PPh(3))(4) which yielded cis-(PPh(3))(2)PtH(tBu(2)P(CH(2))(4)OB(C(6)F(5))(3)) 12, while the reaction of [SIMesH][tBu(2)P(CH(2))(4)OB(C(6)F(5))(3)] 13 with NiCl(2)(DME) and PdCl(2)(PhCN)(2) afforded the complexes [SIMesH](2)[trans-Cl(2)Ni(tBu(2)PC(4)H(8)OB(C(6)F(5))(3))(2)] 14 and [SIMesH](2)[trans-PdCl(2)(tBu(2)P(CH(2))(4)OB(C(6)F(5))(3))(2)] 15, respectively, analogous to those prepared with 4 and 5. Finally, the reaction of 7 and 13with [(p-cymene)RuCl(2)](2) proceeds to give the new orange products [SIMesH][(p-cymene)RuCl(2)(Cy(2)PC(6)F(4)BF(C(6)F(5))(2))] 16 and [SIMesH][(p-cymene)RuCl(2)(tBu(2)P(CH(2))(4)OB(C(6)F(5))(3))] 17, respectively. Crystal structures of 1, 6, 10, 11, 12, and 16 are reported.
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.001 | 0.000 |
| Research integrity | 0.000 | 0.000 |
| Insufficient payload (model declined to judge) | 0.002 | 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".