Nutrition Preference Comparisons
Comparative response examples for investigating which answers satisfy domain-specific requirements more consistently.
Summary and intended purpose
Pairs and small sets of candidate responses to the same clinical nutrition task, annotated with the criteria under which one candidate is preferred. Intended to support preference optimisation workflows and to reveal systematic model behaviours.
Intended purpose
Support post-training workflows that learn from comparisons, and expose where candidate answers diverge on constraint handling and completeness.
Target training or evaluation tasks
- Pairwise preference between candidates on a stated rubric
- Identifying the candidate that correctly acknowledges missing information
- Preferring constraint-compliant over superficially fluent responses
Clinical scope
- Adult clinical nutrition tasks mirroring the instruction dataset
- Comparison criteria focus on constraint adherence, completeness, and safety-relevant omissions
Example record schema
{
"example_id": "npc-0001-synthetic",
"specialty": "clinical_nutrition",
"task_type": "pairwise_preference",
"language": "en",
"scenario": {
"summary": "Adult meal-structure task with a stated energy target and a stated food intolerance.",
"stated_constraints": [
"energy_target_range",
"intolerance_exclusion"
]
},
"candidates": {
"a": {
"response": "<candidate_a>",
"constraints_satisfied": [
"energy_target_range"
]
},
"b": {
"response": "<candidate_b>",
"constraints_satisfied": [
"energy_target_range",
"intolerance_exclusion"
]
}
},
"preference": {
"chosen": "b",
"criteria": [
"constraint_adherence",
"completeness"
],
"confidence": "high",
"label_source": "rubric"
},
"review_status": "automated_only",
"generation_version": "gen-v2"
}Generation methodology
- 01Multiple candidates are generated per task under varied conditions.
- 02Rubric-based scoring produces a preference label and the criteria that drove it.
- 03Ties and low-confidence comparisons are retained with explicit flags rather than discarded.
NoteSynthetic generation does not itself establish factual medical correctness. See the methodology for how generation, automated checks, and expert review are separated.
Validation information
- Preference labels in the research corpus are rubric-derived; they are not individually expert-assigned.
- Expert-labelled subsets can be scoped for engagements that require them.
| Dimension | Current status |
|---|---|
| Automated checks | Rubric scoring, agreement flags, schema validity, duplicate detection |
| Human review coverage | None across the research corpus; expert-labelled subsets by engagement |
| Sample size | To be specified during dataset scoping |
| Known limitations | Rubric-derived labels inherit the rubric's blind spots |
| Evaluation version | To be specified during dataset scoping |
Known limitations
- Not every preference label comes from a clinical expert.
- Rubric-based preferences may reward rubric compliance rather than clinical quality.
- Commercial availability and licence terms must be scoped before use.
Licensing and access process
Licence status: Research access by inquiry. Access is sales-assisted. Licensing is handled by agreement, based on data provenance, rights, permitted uses, delivery, and commercial terms.
- Step 1Inquiry describing the post-training setup and target behaviours.
- Step 2Discussion of rubric alignment and whether expert-labelled subsets are needed.
- Step 3Rights review and written access terms.
Request details, discuss a sample, or ask about review coverage for this category.
Request dataset details