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 (the wishlist estimates about 250 reactions; HTE): 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.
Source: ChemRxiv preprint 10.26434/chemrxiv-2025-qw468 (cobalt-catalysed C(sp2)-H arylation without Grignard reagents; Janssen / TU Wien). About 250 HTE reactions. The reaction data are tables in the SI, which is in the same PDF as the main article. A SMILES list for some chemicals appears later in the SI; the remaining reagents must be converted from names or structures to SMILES. Many results are low-yield or negative, and these are the point of the dataset, so record zero and low yields explicitly and do not drop them. The preprint is CC-BY-NC-ND 4.0. Crossref shows no journal version yet. If one appears, check whether the data changed and cite the version you used.
Known locations:
Outcomes are mostly low or zero yields, so check that ORD outcomes represent failed reactions correctly (product with yield 0, analysis method stated). Data must be transcribed from PDF tables, which risks row/column errors, so spot-checking against the PDF is needed. Only some chemicals have SMILES; the rest need name-to-structure conversion, which is error-prone for catalysts and ligands. The yield type (GC, NMR or isolated) must be taken from the SI text.
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.