Evaluation Datasets and Input Mapping
An evaluation dataset pairs inputs with the information needed to judge results. Map dataset fields to the project’s actual input and output contract.
Before you begin
An accessible project and permission to create or update its evaluation dataset.
Evaluation concepts
Evaluation dataset
A collection of input cases and any expected outputs needed for assessment. Its mappings must match the project inputs and selected output.
Input field
A value collected from a user or client for execution. Map its displayed label to the correct workflow input key.
Expected output
The reference value used by an evaluator when its method requires one. It represents the desired behavior, not necessarily a verbatim answer for every evaluation method.
Schema
A definition of fields, types, required values, and supported constraints. Use it to validate the shape of data; it does not establish factual correctness.
Batch row
One input record processed through the selected project. Check the row’s status and result, not only the batch-level indicator.
Prepare an evaluation dataset
Select the project inputs and output to evaluate.

Select the workflow inputs and expected-output field for the dataset.
Add rows with valid input values and expected output where required by the evaluator.
Review the mapping before generating results.
Each dataset row can run against the intended project fields.
Behavior and limitations
A dataset field label is not necessarily a node ID. An input mapping that does not match the project can fail before scoring. Through the public API, append requests accept 1–100 rows and repeated appends can duplicate rows. Preserve row IDs when updating existing data.
Related resources
Was this helpful?

