Skip to main content
Challenge

Build a Yente Cross-Dataset Entity Resolution Tracer

Trace matching entity profiles across independent screening datasets using OpenSanctions Yente API. Consolidate disjointed jurisdictional sanctions records into unified analyst provenance dossiers.

CybersecurityHosted by Vera
Challenge brief

What you are building

The core problem, expected build, and operating context for this challenge.

Trace matching entity profiles across independent screening datasets using OpenSanctions Yente API. Consolidate disjointed jurisdictional sanctions records into unified analyst provenance dossiers.

Sanctions Quality Assurance Analyst

Ingest cross-jurisdictional screening alerts produced by a local yente matching instance.

Retrieve overlapping entity profiles and FollowTheMoney schema representations from distinct datasets.

Merge matching properties and identify divergent birth dates or aliases across lists.

Generate a consolidated entity profile documenting cross-dataset provenance and discrepancies.

A provenance tree view showing match lineage, raw upstream gazette references, and analyst commentary comparison.

Run a local yente Docker instance indexing standard OpenSanctions default dataset samples. Starter examples below are synthetic. They are not downloaded records.

OpenSanctions data toolkit Query yente match endpoints and FollowTheMoney entity properties to extract lineage metadata.

mastra-ai, pydantic, httpx. Mastra AI supports deterministic state machines and provenance step tracking across complex compliance workflows. Hosted language model to generate structured audit justifications.

Submit runnable source, pinned dependencies, setup commands, a working interface, example outputs, and a recorded end-to-end demo. Include tests and an action log.

Queries local yente instance using FollowTheMoney schema representations.

Extracts source dataset provenance identifiers and published timestamps.

Produces a signed reconciliation dossier documenting dispute resolution grounds.

```json [ { "input": { "target_query": { "name": "Orion Marine Freight", "jurisdiction": "CY" }, "yente_matches": [ { "id": "ftm-1", "datasets": [ "ofac_sdn" ], "properties": { "incorporationDate": [ "2010" ] } }, { "id": "ftm-2", "datasets": [ "eu_fsf" ], "properties": { "incorporationDate": [ "2011" ] } } ] }, "expected_output": { "merged_entity_id": "ftm-merged-01", "source_datasets": [ "ofac_sdn", "eu_fsf" ], "discrepancies_detected": true, "conflicting_fields": [ "incorporationDate" ], "resolution_status": "requires_manual_merge" } }, { "input": { "target_query": { "name": "Atlas Services", "jurisdiction": "DE" }, "yente_matches": [ { "id": "ftm-3", "datasets": [ "un_sc" ], "properties": { "incorporationDate": [ "2005" ] } } ] }, "expected_output": { "merged_entity_id": "ftm-3", "source_datasets": [ "un_sc" ], "discrepancies_detected": false, "conflicting_fields": [], "resolution_status": "clean_single_source" } } ] ```

Simulates sanctions review provenance. All entity mappings and datasets are synthetic or public test fixtures. Use mock external writes. Require human review before any real deployment.

Rules

Participation guide

Simulates sanctions review provenance. All entity mappings and datasets are synthetic or public test fixtures. Use mock external writes and human review.

Delivery guide

How work is evaluated

Evaluation

Queries local yente instance using FollowTheMoney schema representations. Extracts source dataset provenance identifiers and published timestamps. Produces a signed reconciliation dossier documenting dispute resolution grounds.

Submission format

Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.

Datasets

Challenge datasets

Public datasets, plus the private datasets you have access to.

Evaluation rubric

How submissions are scored

These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.

Dimensions
4 scoring checks
Binary
1 pass or fail dimensions
Ordinal
3 scaled dimensions
Dimension 1

Complete workflow

Ingest cross-jurisdictional screening alerts produced by a local yente matching instance. Retrieve overlapping entity profiles and FollowTheMoney schema representations from distinct datasets. Merge matching properties and identify divergent birth dates or aliases across lists. Generate a consolidated entity profile documenting cross-dataset provenance and discrepancies.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 2

Correctness and evidence

Queries local yente instance using FollowTheMoney schema representations. Extracts source dataset provenance identifiers and published timestamps. Produces a signed reconciliation dossier documenting dispute resolution grounds.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 3

Review interface

A provenance tree view showing match lineage, raw upstream gazette references, and analyst commentary comparison.

Score scale
012
Score 0

Missing or incorrect.

Score 1

Partly complete, with documented gaps.

Score 2

Complete, with reproducible evidence.

Dimension 4

Safe execution

Simulates sanctions review provenance. All entity mappings and datasets are synthetic or public test fixtures.

Binary check

This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.

Learning goals

What you should walk away with

  • Ingest cross-jurisdictional screening alerts produced by a local yente matching instance.

  • Retrieve overlapping entity profiles and FollowTheMoney schema representations from distinct datasets.

  • Merge matching properties and identify divergent birth dates or aliases across lists.

  • Generate a consolidated entity profile documenting cross-dataset provenance and discrepancies.

Resources and assets

Reference links and supporting material

Dataset notes

Run a local yente Docker instance indexing standard OpenSanctions default dataset samples. Supplied starter examples are synthetic, not source extracts.

Challenge setup

Configuration summary for this challenge.

Challenge input

Input details are not configured.

Mastra AI

TypeScript agent framework.

Evaluated output

No output checks are configured.

Evaluation checks
  • Ingest cross-jurisdictional screening alerts produced by a local yente matching instance. Retrieve overlapp...
  • Queries local yente instance using FollowTheMoney schema representations. Extracts source dataset provenanc...
  • A provenance tree view showing match lineage, raw upstream gazette references, and analyst commentary compa...
Configured evaluation evidence
  • 2 public reference cases
Configured runtime
  • 2 configured tools

Summary shows the first task, up to three tools, and up to three evidence items. Open the technical recipe to view all configured items.

View technical recipe

Configured tools

Action Space
  • Mastra AI · Optional
Orchestration
  • Mastra AI · Optional

Evaluation contract

  • Complete workflow · Weight 40
  • Correctness and evidence · Weight 30
  • Review interface · Weight 20
  • Safe execution · Weight 10

Reference cases

  • 2 public reference cases

Workflow tasks

No workflow tasks are configured.

Recipe freeze marker

No recipe freeze time is recorded.

Frequently Asked Questions about Build a Yente Cross-Dataset Entity Resolution Tracer