Datasets:
uid string | dataset_id string | jurisdiction string | court_level string | year int64 | area_of_law string | pillar string | series string | input_obligation_text string | input_deadline string | input_responsible_owner string | input_required_proof string | input_action_log_summary string | input_current_status_summary string | question string | ground_truth_label string | ground_truth_rationale string | outcome_signal string | early_window_months int64 | source_citation string |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
UN-TR-001 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | UK | High Court | 2,023 | Commercial | adjudicative_process | 2C | Undertaking: serve amended particulars on defendant | 2023-09-15 | Fee earner A | Proof: service email and certificate | Drafted and served 2023-09-14; filed certificate | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | coherent | Deadline owner action and proof align. | stable | 0 | Synthetic |
UN-TR-002 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | UK | High Court | 2,023 | Commercial | adjudicative_process | 2C | Undertaking: serve amended particulars | 2023-09-15 | Owner not assigned | Proof: service email and certificate | Action log says served but no certificate saved | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | incoherent | Owner missing and proof not linked despite claimed compliance. | breach_risk | 0 | Synthetic |
UN-TR-003 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | US | Federal | 2,022 | Employment | adjudicative_process | 2C | Order: produce documents responsive to request set 1 | 2022-06-10 | Associate B | Proof: production letter and bates range | Produced 2022-06-09 with cover letter | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | coherent | Production matches order with proof. | stable | 0 | Synthetic |
UN-TR-004 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | US | Federal | 2,022 | Employment | adjudicative_process | 2C | Order: produce documents set 1 | 2022-06-10 | Associate B | Proof: production letter and bates range | Action log: preparing production | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | incoherent | Status claims compliance but actions show not complete. | breach_risk | 0 | Synthetic |
UN-TR-005 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | UK | County Court | 2,022 | Property | adjudicative_process | 2C | Order: file witness statements | 2022-11-01 | Fee earner C | Proof: filed statement timestamp | Filed 2022-10-31; receipt saved | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | coherent | Filed before deadline with proof. | stable | 0 | Synthetic |
UN-TR-006 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | UK | County Court | 2,022 | Property | adjudicative_process | 2C | Order: file witness statements | 2022-11-01 | Fee earner C | Proof: filed statement timestamp | Action log: drafted only; no filing receipt | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | incoherent | No proof of filing. | breach_risk | 1 | Synthetic |
UN-TR-007 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | EU | Commercial Court | 2,020 | Commercial | adjudicative_process | 2C | Undertaking: pay invoice into escrow | 2020-03-20 | Partner D | Proof: bank transfer receipt | Paid 2020-03-19; receipt saved | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | coherent | Payment and proof align. | stable | 0 | Synthetic |
UN-TR-008 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | EU | Commercial Court | 2,020 | Commercial | adjudicative_process | 2C | Undertaking: pay into escrow | 2020-03-20 | Partner D | Proof: bank receipt | Action log: intended payment | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | incoherent | No proof and action incomplete. | breach_risk | 0 | Synthetic |
UN-TR-009 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | UK | Tribunal | 2,021 | Employment | adjudicative_process | 2C | Order: lodge schedule of loss | 2021-05-05 | Paralegal E | Proof: email to tribunal and copy attached | Sent 2021-05-04; email saved | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | coherent | Clear compliance record. | stable | 0 | Synthetic |
UN-TR-010 | legal-undertaking-order-obligation-compliance-coherence-risk-v0.1 | UK | Tribunal | 2,021 | Employment | adjudicative_process | 2C | Order: lodge schedule of loss | 2021-05-05 | Paralegal E | Proof: email to tribunal | Sent email but attachment missing | Status: complied | Is obligation compliance coherent. Answer coherent or incoherent. | incoherent | Proof incomplete due to missing attachment. | breach_risk | 0 | Synthetic |
What this dataset does
You receive
obligation text deadline owner required proof action log status
You decide
coherent or incoherent
Daily use
order compliance tracking
breach risk flagging
missing proof detection
- Downloads last month
- 10