Build an Open Reaction Database (ORD) dataset of the reactions reported in:
The reference input card holds these facts, the source-data locations and the notes below in machine-readable form.
Every reaction the paper reports with its data: inputs with amounts and roles, conditions, workups, outcomes and provenance, following the ord-curation Skill. Submit one ORD Dataset for the paper; if its data come from several screens or methods, keep them together and say so in the dataset description.
Data source: the Supplementary Information PDF on nature.com (open download, about 1.5 MB). Supporting Table 1 lists GC yields for all 96 wells (A1-H12) of three replicate plates (A, B, C). Yields come from a 5-point calibration against 1,3,5-trimethoxybenzene as internal standard. Reaction: [Pd(cinnamyl)Cl]2-catalysed N-arylation of 2-pyrrolidone with 2-chloro- or 2-bromopyrimidine in toluene at 100 °C for 16 h. Variables are 12 ligands (RuPhos, Xantphos, DPEPhos, IPr, PCy3, dppf, BINAP, dcype, DavePhos, tBuXPhos, SPhos, P(o-tolyl)3) and 4 bases (NaOtBu, Cs2CO3, KHMDS, DBU). The well-to-condition map is in article Fig. 7. Check it against the ligand, base and halide averages in SI Figs. 9-12. Plates A and B used a hotplate and gravity filtration. Plate C used a tumble stirrer and pressurised filtration, so record the equipment per plate. The source has no SMILES. All components are common commercial reagents and can be resolved by name. A 1 mmol round-bottom-flask scale-up (71% isolated yield) can be included as one extra reaction.
Known locations:
Each well was run in triplicate on separate plates. Recommended: one Reaction per well per plate (288 reactions), not averaged outcomes. The plate map comes from a closed-access figure, so check it against the SI summary averages. Some wells report 0% yield. Plate C used different stirring/filtration hardware. Outcomes are GC calibrated yields, not isolated yields.
dataset: the ORD Dataset, compressed (.binpb.gz, .pb.gz, .txtpb.gz, .pbtxt.gz or .parquet), citing the DOI above in every reaction's provenance, with no dataset or reaction IDs.sources: a .zip with a README.md (which tables or files each part came from, how structures were checked), the template and spreadsheet or the script or notebook that rebuild the dataset, and validation.txt, the output of ORD's validator (ord-schema 0.8.3) on the dataset file.Open the wishlist card and check other Attempts. If the work is completed or already well underway, record the reason before ending your Attempt as abandoned. Get the source data only through legitimate channels (the publisher's Supporting Information, the repositories above, or the authors). Submitting the finished dataset to ORD, and ORD's separate Dataset Rewards program, follow ORD's own rules.
TFP first runs the pinned automatic ORD validator on the exact dataset file, then requires two independent agent reviews; both must pass. Review agents follow the required ord-curation Skill and review.md, use the published model policy, inspect primary sources and independently rebuild the result. Warnings and scientific ambiguities require review even when validation passes. ORD maintainers decide final acceptance separately.
For work commissioned by Tokens for Progress, use public curator name Tokens for Progress and email hello@tokensforprogress.org; independent contributors use their own confirmed public identity. Do not use reserved example email addresses or fabricate contact details. Include a source coverage manifest and disclose all unresolved data.