Upload 2 files
Browse files- Legal_Reasoning_Task_Examples.parquet +2 -2
- README.md +283 -56
Legal_Reasoning_Task_Examples.parquet
CHANGED
|
@@ -1,3 +1,3 @@
|
|
| 1 |
version https://git-lfs.github.com/spec/v1
|
| 2 |
-
oid sha256:
|
| 3 |
-
size
|
|
|
|
| 1 |
version https://git-lfs.github.com/spec/v1
|
| 2 |
+
oid sha256:174110d6c564fa3dad50d7102823f377671e3d3e13e11f74fcf2aceb4f148ecf
|
| 3 |
+
size 153261
|
README.md
CHANGED
|
@@ -1,91 +1,318 @@
|
|
| 1 |
---
|
| 2 |
-
license:
|
| 3 |
language:
|
| 4 |
- en
|
| 5 |
-
|
| 6 |
-
- legal
|
| 7 |
-
- law
|
| 8 |
-
- corporate-law
|
| 9 |
-
- mergers-and-acquisitions
|
| 10 |
-
- evaluation
|
| 11 |
-
- rubrics
|
| 12 |
-
- llm-evaluation
|
| 13 |
-
pretty_name: Legal Tasks Sample Set (Tasks 89 & 93)
|
| 14 |
size_categories:
|
| 15 |
- n<1K
|
| 16 |
task_categories:
|
| 17 |
- text-generation
|
| 18 |
- question-answering
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 19 |
---
|
| 20 |
|
| 21 |
-
#
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 22 |
|
| 23 |
-
##
|
| 24 |
|
| 25 |
-
|
|
|
|
|
|
|
| 26 |
|
| 27 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 28 |
|
| 29 |
## Contents
|
| 30 |
|
| 31 |
-
|
| 32 |
-
|
| 33 |
-
|
|
| 34 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 35 |
|
| 36 |
-
|
|
|
|
| 37 |
|
| 38 |
-
|
| 39 |
|
| 40 |
-
|
| 41 |
-
|
| 42 |
-
|
| 43 |
|
| 44 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 45 |
|
| 46 |
| Field | Type | Description |
|
| 47 |
-
|---
|
| 48 |
-
| `
|
| 49 |
-
| `
|
| 50 |
-
| `
|
| 51 |
-
| `
|
| 52 |
-
|
| 53 |
-
|
| 54 |
-
|
| 55 |
-
|
| 56 |
-
|
| 57 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 58 |
|
| 59 |
-
##
|
| 60 |
|
| 61 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 62 |
|
| 63 |
-
|
| 64 |
-
- `score_option` — the points available for meeting the criterion.
|
| 65 |
-
- `criterion` — the specific thing being evaluated.
|
| 66 |
-
- `justification` — why the criterion matters.
|
| 67 |
|
| 68 |
-
|
|
|
|
|
|
|
|
|
|
| 69 |
|
| 70 |
-
|
| 71 |
|
| 72 |
-
|
| 73 |
-
- Studying rubric-based scoring of long-form legal responses
|
| 74 |
-
- Illustrating how legal evaluation tasks are constructed and refined across versions
|
| 75 |
|
| 76 |
-
|
|
|
|
| 77 |
|
| 78 |
-
|
| 79 |
|
| 80 |
-
-
|
| 81 |
-
-
|
|
|
|
| 82 |
|
| 83 |
-
|
| 84 |
|
| 85 |
-
-
|
| 86 |
-
-
|
| 87 |
-
-
|
| 88 |
|
| 89 |
-
|
|
|
|
|
|
|
| 90 |
|
| 91 |
-
|
|
|
|
|
|
| 1 |
---
|
| 2 |
+
license: cc-by-nc-4.0
|
| 3 |
language:
|
| 4 |
- en
|
| 5 |
+
pretty_name: 'Human Edge Legal Reasoning Evaluation — Showcase Sample'
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 6 |
size_categories:
|
| 7 |
- n<1K
|
| 8 |
task_categories:
|
| 9 |
- text-generation
|
| 10 |
- question-answering
|
| 11 |
+
tags:
|
| 12 |
+
- legal
|
| 13 |
+
- law
|
| 14 |
+
- legal-reasoning
|
| 15 |
+
- evaluation
|
| 16 |
+
- rubric
|
| 17 |
+
- rubrics
|
| 18 |
+
- reward-model
|
| 19 |
+
- rlhf
|
| 20 |
+
- rlvr
|
| 21 |
+
- expert-annotation
|
| 22 |
+
- benchmark
|
| 23 |
+
configs:
|
| 24 |
+
- config_name: default
|
| 25 |
+
data_files:
|
| 26 |
+
- split: train
|
| 27 |
+
path: legal_reasoning_showcase.parquet
|
| 28 |
+
dataset_info:
|
| 29 |
+
features:
|
| 30 |
+
- name: task_id
|
| 31 |
+
dtype: int32
|
| 32 |
+
- name: area
|
| 33 |
+
dtype: string
|
| 34 |
+
- name: prompt
|
| 35 |
+
dtype: string
|
| 36 |
+
- name: golden_answer
|
| 37 |
+
dtype: string
|
| 38 |
+
- name: associated_rubrics
|
| 39 |
+
dtype: int32
|
| 40 |
+
- name: rubrics
|
| 41 |
+
list:
|
| 42 |
+
- name: rubric_category
|
| 43 |
+
dtype: string
|
| 44 |
+
- name: score_option
|
| 45 |
+
dtype: int32
|
| 46 |
+
- name: criterion
|
| 47 |
+
dtype: string
|
| 48 |
+
- name: justification
|
| 49 |
+
dtype: string
|
| 50 |
+
- name: task_details
|
| 51 |
+
dtype: string
|
| 52 |
+
- name: reference_materials
|
| 53 |
+
dtype: string
|
| 54 |
+
- name: realistic_explanation
|
| 55 |
+
dtype: string
|
| 56 |
+
- name: difficulty_explanation
|
| 57 |
+
dtype: string
|
| 58 |
+
- name: peer_review_1_overall_quality_label
|
| 59 |
+
dtype: string
|
| 60 |
+
- name: peer_review_1_overall_quality_description
|
| 61 |
+
dtype: string
|
| 62 |
+
- name: peer_review_1_representativeness_label
|
| 63 |
+
dtype: string
|
| 64 |
+
- name: peer_review_1_difficulty_label
|
| 65 |
+
dtype: string
|
| 66 |
+
- name: peer_review_1_difficulty_description
|
| 67 |
+
dtype: string
|
| 68 |
+
- name: peer_review_1_task_specification_quality_label
|
| 69 |
+
dtype: string
|
| 70 |
+
- name: peer_review_2_overall_quality_label
|
| 71 |
+
dtype: string
|
| 72 |
+
- name: peer_review_2_overall_quality_description
|
| 73 |
+
dtype: string
|
| 74 |
+
- name: peer_review_2_representativeness_label
|
| 75 |
+
dtype: string
|
| 76 |
+
- name: peer_review_2_difficulty_label
|
| 77 |
+
dtype: string
|
| 78 |
+
- name: peer_review_2_difficulty_description
|
| 79 |
+
dtype: string
|
| 80 |
+
- name: peer_review_2_task_specification_quality_label
|
| 81 |
+
dtype: string
|
| 82 |
+
splits:
|
| 83 |
+
- name: train
|
| 84 |
+
num_examples: 6
|
| 85 |
---
|
| 86 |
|
| 87 |
+
# Human Edge — Legal Reasoning Evaluation (Showcase Sample)
|
| 88 |
+
|
| 89 |
+
A public 6-task sample from a rubric-based legal reasoning evaluation dataset built by
|
| 90 |
+
**Human Edge** ([humanedgetech.ai](https://humanedgetech.ai)). Each task is authored and reviewed by
|
| 91 |
+
practicing senior lawyers and is designed to produce a **verifiable, per-criterion reward signal**
|
| 92 |
+
for post-training and evaluation of frontier language models on high-complexity legal work.
|
| 93 |
+
|
| 94 |
+
The sample contains **one task per legal subdomain**, drawn from a larger internal corpus of
|
| 95 |
+
50 expert-authored tasks.
|
| 96 |
|
| 97 |
+
## Why this dataset exists
|
| 98 |
|
| 99 |
+
Most legal evaluations reduce to multiple-choice recall or bar-exam-style questions. Real legal work
|
| 100 |
+
does not look like that: it is open-ended, multi-jurisdictional, and judged on reasoning quality,
|
| 101 |
+
appropriate hedging, and whether the sources actually say what the answer claims they say.
|
| 102 |
|
| 103 |
+
This dataset takes the opposite approach. Every task is a realistic instruction from a practicing
|
| 104 |
+
lawyer's desk, paired with an expert-authored reference answer and a **fine-grained rubric of
|
| 105 |
+
weighted, binary criteria** (20–40 across the source corpus).
|
| 106 |
+
The rubric — not the reference answer — is the object of
|
| 107 |
+
evaluation. That makes scoring reproducible across graders and directly convertible into
|
| 108 |
+
per-dimension reward signals.
|
| 109 |
+
|
| 110 |
+
## Task architecture
|
| 111 |
+
|
| 112 |
+
Each row is a triple-component unit:
|
| 113 |
+
|
| 114 |
+
| Component | Field | What it is |
|
| 115 |
+
|---|---|---|
|
| 116 |
+
| 1. Legal reasoning prompt | `prompt` | A realistic scenario requiring multi-step reasoning and professional judgment, with role, jurisdiction, and deliverable format specified |
|
| 117 |
+
| 2. Golden answer | `golden_answer` | An expert-authored reference analysis (17k–38k characters in this sample) |
|
| 118 |
+
| 3. Scoring rubric | `rubrics` | 20–40 categorized, weighted, binary criteria, each with the author's justification |
|
| 119 |
+
|
| 120 |
+
## Rubric design
|
| 121 |
+
|
| 122 |
+
Criteria are binary and weighted. Positive weights reward required content; negative weights
|
| 123 |
+
penalize specific failure modes (hallucinated authority, overconfident advice, missing caveats).
|
| 124 |
+
|
| 125 |
+
Criteria fall into four categories, with Substance further divided into four sub-categories:
|
| 126 |
+
|
| 127 |
+
| Category | Sub-category | Criteria | What it tests |
|
| 128 |
+
|---|---|---|---|
|
| 129 |
+
| **Substance** | Explicit requirements | 27 | Did the answer do what was literally asked? |
|
| 130 |
+
| | Implicit requirements | 27 | Did it surface what a competent practitioner would raise unprompted? |
|
| 131 |
+
| | Legal correctness | 21 | Is the law stated accurately? |
|
| 132 |
+
| | Reasoning quality | 31 | Is the analytical path sound, not just the conclusion? |
|
| 133 |
+
| **Sources & References** | — | 34 | Are cited authorities real, relevant, and correctly characterized? |
|
| 134 |
+
| **Structure & Style** | — | 30 | Does it read like professional work product? |
|
| 135 |
+
| **Negative Criteria** | — | 25 | Penalties for specific, anticipated failure modes |
|
| 136 |
+
| **Total** | | **195** | |
|
| 137 |
+
|
| 138 |
+
The `rubric_category` field stores each of these as a single literal string. Filter on these values
|
| 139 |
+
exactly:
|
| 140 |
+
|
| 141 |
+
`Substance Rubric - Explicit requirements`, `Substance Rubric - Implicit requirements`,
|
| 142 |
+
`Substance Rubric - Legal correctness`, `Substance Rubric - Reasoning quality`,
|
| 143 |
+
`Sources and References Rubric`, `Structure & Style Rubric`, `Negative Rubric`
|
| 144 |
+
|
| 145 |
+
Weight distribution across the 195 criteria in this sample:
|
| 146 |
+
`+5` (69), `+3` (70), `+1` (31), `-1` (2), `-3` (5), `-5` (18).
|
| 147 |
|
| 148 |
## Contents
|
| 149 |
|
| 150 |
+
Six tasks, one per subdomain:
|
| 151 |
+
|
| 152 |
+
| `task_id` | `area` | Rubric criteria | Peer review overall quality (R1 / R2) |
|
| 153 |
+
|---|---|---|---|
|
| 154 |
+
| 18 | Employment & Labor | 34 | 3 / 4 |
|
| 155 |
+
| 40 | Intellectual Property (IP) | 40 | 4 / 4 |
|
| 156 |
+
| 68 | Commercial Litigation | 34 | 4 / 5 |
|
| 157 |
+
| 82 | Regulatory & Compliance | 29 | 4 / 5 |
|
| 158 |
+
| 93 | Corporate & M&A | 30 | 4 / 4 |
|
| 159 |
+
| 100 | Contract Law | 28 | 4 / 5 |
|
| 160 |
|
| 161 |
+
Jurisdictions are US and UK (England and Wales). `task_id` values are the original corpus
|
| 162 |
+
identifiers and are intentionally non-contiguous.
|
| 163 |
|
| 164 |
+
## Who wrote and reviewed these tasks
|
| 165 |
|
| 166 |
+
Tasks were authored by senior legal practitioners recruited against a hard credential bar:
|
| 167 |
+
8+ years in practice, a Master's or PhD in law, and a background in AmLaw 100 / Magic Circle firms,
|
| 168 |
+
senior courts, government, or in-house at large enterprises.
|
| 169 |
|
| 170 |
+
The contributing cohort averaged **~18.5 years of practice**, split roughly 75% US / 25% UK,
|
| 171 |
+
with education spanning T14 US law schools and leading UK and European universities. Identity was
|
| 172 |
+
verified for every contributor before any project interaction.
|
| 173 |
+
|
| 174 |
+
Domain expertise alone does not make a calibrated evaluator, so every contributor completed a
|
| 175 |
+
mandatory training program (~2.3 hours average) on stress-testing model outputs, applying rubrics
|
| 176 |
+
consistently, and documenting rationale.
|
| 177 |
+
|
| 178 |
+
## Quality assurance
|
| 179 |
+
|
| 180 |
+
Three stages, applied to every task in the source corpus:
|
| 181 |
+
|
| 182 |
+
1. **Automated checks.** Every task passes programmatic validation before it reaches a reviewer.
|
| 183 |
+
Prompts are checked for scenario framing, role specification, deliverable format, and
|
| 184 |
+
jurisdictional context. Rubrics are checked for binary format compliance and a minimum criterion
|
| 185 |
+
count. A model-graded pass confirms each rubric is consistent with its golden answer.
|
| 186 |
+
2. **Double-blind expert peer review.** Two independent senior practitioners review each task,
|
| 187 |
+
rating overall quality, difficulty, representativeness, and task specification quality, each with
|
| 188 |
+
written rationale. Reviews drive iterative revision rather than a simple accept/reject: the author
|
| 189 |
+
revises against reviewer comments, and the version shipped here reflects those revisions.
|
| 190 |
+
3. **Difficulty validation.** Tasks are stress-tested against frontier models. A task is admitted
|
| 191 |
+
only if strong models still fail a meaningful share of its rubric criteria — tasks that models
|
| 192 |
+
solve comfortably carry no training signal and are rejected.
|
| 193 |
+
|
| 194 |
+
Tasks in the source corpus averaged roughly eleven hours of expert effort each, counting authoring,
|
| 195 |
+
peer review, and revision. Reviewer ratings clustered tightly, indicating consensus among
|
| 196 |
+
practitioners rather than averaged-out disagreement.
|
| 197 |
+
|
| 198 |
+
## Field reference
|
| 199 |
+
|
| 200 |
+
### Task content
|
| 201 |
+
|
| 202 |
+
| Field | Type | Description |
|
| 203 |
+
|---|---|---|
|
| 204 |
+
| `task_id` | int32 | Original corpus identifier |
|
| 205 |
+
| `area` | string | Legal subdomain |
|
| 206 |
+
| `prompt` | string | The legal reasoning prompt given to the model |
|
| 207 |
+
| `golden_answer` | string | Expert-authored reference answer |
|
| 208 |
+
| `associated_rubrics` | int32 | Number of rubric criteria; always equals `len(rubrics)` |
|
| 209 |
+
| `rubrics` | list<struct> | Nested rubric criteria (see below) |
|
| 210 |
+
| `task_details` | string | Author's note on why the task is hard or interesting |
|
| 211 |
+
| `reference_materials` | string | Source authorities relied on; free-text, sometimes URLs, sometimes citations |
|
| 212 |
+
|
| 213 |
+
### `rubrics` struct
|
| 214 |
|
| 215 |
| Field | Type | Description |
|
| 216 |
+
|---|---|---|
|
| 217 |
+
| `rubric_category` | string | One of the seven literal values listed above |
|
| 218 |
+
| `score_option` | int32 | Weight: `+5`, `+3`, `+1`, `-1`, `-3`, `-5` |
|
| 219 |
+
| `criterion` | string | Binary question applied to the model's answer |
|
| 220 |
+
| `justification` | string | Author's rationale for why this criterion matters |
|
| 221 |
+
|
| 222 |
+
Text has been normalized: non-breaking spaces, stray tabs and other exotic whitespace introduced
|
| 223 |
+
by the authoring tools have been folded to plain spaces. Newlines in `golden_answer` are preserved.
|
| 224 |
+
|
| 225 |
+
### Author commentary
|
| 226 |
+
|
| 227 |
+
The task author's own notes on realism and difficulty. Their numeric self-ratings are deliberately
|
| 228 |
+
**not** included — an author's rating of their own task is not independent evidence, so the only
|
| 229 |
+
ratings in this dataset come from the two peer reviewers.
|
| 230 |
+
|
| 231 |
+
| Field | Type | Description |
|
| 232 |
+
|---|---|---|
|
| 233 |
+
| `realistic_explanation` | string | Why the scenario reflects real practice |
|
| 234 |
+
| `difficulty_explanation` | string | What makes the task hard, and where models are expected to fail |
|
| 235 |
+
|
| 236 |
+
### Peer review
|
| 237 |
+
|
| 238 |
+
Two independent reviewers per task, both prefixed: `peer_review_1_` is the first-round review
|
| 239 |
+
(conducted on the first draft version), `peer_review_2_` the second (conducted on the second draft
|
| 240 |
+
version). The final version shipped here was produced after revising comments from the second
|
| 241 |
+
reviewer. Reviewer identities are not published.
|
| 242 |
+
|
| 243 |
+
The `*_label` fields carry the rating exactly as the reviewer selected it — score and wording
|
| 244 |
+
together, e.g. `4 - Above Standards`. To get a numeric value, split on the first `-`.
|
| 245 |
+
|
| 246 |
+
| Field suffix | Type | Description |
|
| 247 |
+
|---|---|---|
|
| 248 |
+
| `overall_quality_label` | string | Rating 1–5, e.g. `4 - Above Standards` |
|
| 249 |
+
| `overall_quality_description` | string | Reviewer's written rationale for the quality rating |
|
| 250 |
+
| `representativeness_label` | string | Rating 1–5 — how typical this task is of real practice, e.g. `5 - Core Activity` |
|
| 251 |
+
| `difficulty_label` | string | Rating 1–5, e.g. `3 - Moderate` |
|
| 252 |
+
| `difficulty_description` | string | Reviewer's written rationale for the difficulty rating |
|
| 253 |
+
| `task_specification_quality_label` | string | Categorical: `Well-Specified`, `Overspecified`, or `Underspecified` |
|
| 254 |
+
|
| 255 |
+
Rating scales, as presented to reviewers:
|
| 256 |
+
|
| 257 |
+
- **Overall quality:** `1 - Far Below Standards`, `2 - Below Standards`, `3 - Meets Minimum Standards`, `4 - Above Standards`, `5 - Exemplary`
|
| 258 |
+
- **Representativeness:** `1 - Rarely Encountered`, `2 - Uncommon`, `3 - Somewhat Typical`, `4 - Typical`, `5 - Core Activity`
|
| 259 |
+
- **Difficulty:** `1 - Trivial` → `5 - Very Hard` (`3 - Moderate`, `4 - Hard`)
|
| 260 |
+
- **Task specification quality:** `Underspecified`, `Well-Specified`, `Overspecified`
|
| 261 |
+
|
| 262 |
+
## Intended uses
|
| 263 |
+
|
| 264 |
+
- Evaluating LLM performance on open-ended, high-complexity legal reasoning
|
| 265 |
+
- Rubric-as-reward research: RLVR, reward model training, process supervision
|
| 266 |
+
- LLM-as-judge calibration — the rubrics give a judge concrete, verifiable criteria instead of a
|
| 267 |
+
vague quality prompt
|
| 268 |
+
- Studying legal-domain failure modes, especially source and citation reliability
|
| 269 |
+
- A reference template for anyone constructing expert-authored rubric evaluations in other
|
| 270 |
+
professional domains
|
| 271 |
|
| 272 |
+
## Limitations
|
| 273 |
|
| 274 |
+
- **Six tasks.** This is a methodology sample, not a benchmark. Do not report aggregate scores over
|
| 275 |
+
six tasks as a model capability claim.
|
| 276 |
+
- **Scoring requires a judge.** Criteria are binary but not mechanically checkable; they need a
|
| 277 |
+
competent grader, human or model. Judge choice will shift absolute scores.
|
| 278 |
+
- **US and UK only.** Nothing here generalizes to civil law systems, EU-level practice, or other
|
| 279 |
+
common law jurisdictions without revalidation.
|
| 280 |
+
- **Contamination risk.** Published openly, these tasks may enter future training corpora. Treat
|
| 281 |
+
results on this sample as indicative once models trained after its publication are involved.
|
| 282 |
+
- **Reviewer identities are withheld.** Cohort-level credentials are described above; individual
|
| 283 |
+
names and affiliations are not published.
|
| 284 |
+
- **Not legal advice.** The golden answers are evaluation artifacts written against hypothetical
|
| 285 |
+
facts. They are not advice and must not be relied on.
|
| 286 |
|
| 287 |
+
## About Human Edge
|
|
|
|
|
|
|
|
|
|
| 288 |
|
| 289 |
+
Human Edge builds audit-grade expert judgment infrastructure for AI labs: sourcing credentialed
|
| 290 |
+
professionals, training them as calibrated evaluators, and producing rubric-based evaluation data
|
| 291 |
+
with full provenance — who judged, their qualifications, their rationale, and the revision history
|
| 292 |
+
behind every task.
|
| 293 |
|
| 294 |
+
Contact: [humanedgetech.ai](https://humanedgetech.ai)
|
| 295 |
|
| 296 |
+
## License
|
|
|
|
|
|
|
| 297 |
|
| 298 |
+
Released under [**CC BY-NC 4.0**](https://creativecommons.org/licenses/by-nc/4.0/)
|
| 299 |
+
(Creative Commons Attribution-NonCommercial 4.0 International).
|
| 300 |
|
| 301 |
+
**You may**, at no cost:
|
| 302 |
|
| 303 |
+
- Use the dataset to evaluate, benchmark, and audit models
|
| 304 |
+
- Share and redistribute it, in whole or in part
|
| 305 |
+
- Adapt it — build derived rubrics, translate it, extend the schema — and publish those adaptations
|
| 306 |
|
| 307 |
+
**Conditions:**
|
| 308 |
|
| 309 |
+
- **Attribution.** Credit Human Edge and link back to this dataset.
|
| 310 |
+
- **NonCommercial.** Commercial use requires a separate license. This includes training or
|
| 311 |
+
fine-tuning models that are sold or offered as a paid service.
|
| 312 |
|
| 313 |
+
**Commercial use, including model training:** contact Human Edge at
|
| 314 |
+
[humanedgetech.ai](https://humanedgetech.ai). Commercial terms are readily available, and we
|
| 315 |
+
license the full corpus and custom expert-authored datasets in other professional domains.
|
| 316 |
|
| 317 |
+
Nothing in this license grants rights in the third-party statutes, regulations, and court opinions
|
| 318 |
+
cited within the tasks; those remain governed by their own terms.
|