AI annotation & evaluation
Legal rules and formalization
Turn legal provisions and business rules into reviewable logical structures. We identify actors, conditions, obligations and exceptions, review Prolog rules and predicate mappings, and retain the source evidence behind revisions. Projects can review an existing draft or create annotations to an agreed specification.
Request a sample ↗What to confirm before requesting a quote
- Coverage
- Regions, languages, date range and available record count
- Fields and attachments
- Field definitions, example records and whether original documents or media are required
- Quality and updates
- Deduplication and missing-value rules, sample-based acceptance criteria and update frequency
- Permitted uses
- Internal research, model training, customer-facing products or redistribution
These are project scoping questions, not a statement that every data type includes all coverage or permissions.
01 / WHAT’S INCLUDED
What’s in the dataset
- Source provisions, clause references and versions
- Actors, atomic elements, conditions, obligations and exceptions
- Prolog rules, explanations and predicate/argument mappings
- Applicability decisions, disagreements and revision notes
02 / USE CASES
Where it can help
- Legal AI and executable-rule data
- Regulatory knowledge bases and rule consistency checks
- Legal reasoning and rule-trigger evaluation
03 / DELIVERY
Choose the data you need
Receive Excel or JSON linking provisions, rules, code and mappings, with annotation guidance and review notes.
Calibrate conditions, exceptions and disagreement handling on representative provisions before agreeing the full annotation and acceptance scope.
See a sample format ↗Assess the fit for your project
Define the rule behavior to test, then align the source provision, logical structure and code.
Can you review an existing Prolog draft?
Yes. Supply the complete provision, draft, mappings and examples so we can check missing conditions, AND/OR relations, variable types and supporting text.
Can I request structured text without code?
Yes. A project can cover elements, conditions, exceptions and relationships only. Agree the output schema and domain review during the pilot.
Sources and usage
Agree jurisdiction, legal version, logical representation and domain review. Our code-related work here focuses on legal logic and Prolog.
If you plan to train a model, use the data in a customer-facing product or share it with third parties, mention this when requesting a quote so we can check source permissions and restrictions.
Public access does not establish permission for collection, training or redistribution. Naming a platform does not imply affiliation, agency or endorsement.
Read about data sources and rights ↗Want to review a sample first?
Tell us your project objectives and we’ll help you assess and find a relevant sample.