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 12,000 reactions; HTE flow photo): 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: https://github.com/LJM-1997/NCOMMS-24-15301-T (MIT). The file 'AI-assisted cross-species prediction/Data/Photocatalysis_data.xlsx' holds 12,000 rows of microfluidic photocatalytic condition screening. It varies substrate (S-1..S-5), Ir photocatalyst (Ir-1..Ir-5), monitoring wavelength, substrate concentration, catalyst loading, flow rate and laser power, and reports in-line UV absorbance ('non_stable' and 'stable'). The larger 'AI-assisted absorbance prediction/Dataset/dataset.xlsx' (10.8 MB) covers the same 12,000 experiments plus 40 time-resolved absorbance readings per row. Choose one file as the source to avoid duplicates. Only codes identify the substrates and photocatalysts, so take their structures, the reaction and the product from the paper and its SI (https://doi.org/10.1038/s41467-024-53204-6). The outcome is absorbance, not yield, so decide how the ORD outcome represents it and document that choice.
Known locations:
Outcomes are UV absorbance values (a proxy for conversion), not yields, so they need a custom or analytical measurement encoding. These are continuous-flow microfluidic reactions characterized by flow rate and light intensity. Products may not be characterized for each run. Two repo files overlap. There are 12,000 near-identical reaction records with a small chemical space.
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.