Cross-Border LEI Entity Resolution Pipeline with LlamaIndex and Jimdo
Cross-border payments are frequently stalled by disjointed Legal Entity Identifier (LEI) records and unverified corporate hierarchy data. Build an entity resolution pipeline using LlamaIndex RAG agents and Jimdo web tooling to consolidate multi-source entity data and match counterparty identities accurately. Reduce unresolved cross-border entity verification failures to under 2%.
What you are building
The core problem, expected build, and operating context for this challenge.
Construct an automated cross-border entity resolution system using LlamaIndex and Jimdo tools to parse and verify corporate LEI records.
How work is evaluated
Evaluates accuracy of matching noisy counterparty string inputs to validated LEI entity records.
Shared data for this challenge
Review public datasets and any private uploads tied to your build.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
exact_lei_match
Verifies matched LEI string matches target exact LEI
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
resolution_recall
Proportion of valid LEI entities successfully resolved • target: 0.98 • range: 0-1
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Index corporate registry filings and GLEIF records with LlamaIndex vector indices
Integrate Jimdo web extraction tools to fetch dynamic company profile web updates
Perform fuzzy matching and graph disambiguation on ambiguous legal entity names
Generate verifiable entity confidence vectors for payment engine ingestion
Reference links and supporting material
Dataset of 500 entity records with simulated corporate typos, variations, and missing address components mapped to standard LEIs.
How this agent runs
Evaluates accuracy of matching noisy counterparty string inputs to validated LEI entity records.
Challenge input
JSON containing entity name, address string, jurisdiction code
LlamaIndex
Primary framework for vector retrieval
Jimdo
Web content and identity signal extraction
Evaluated output
JSON containing matched LEI, canonical name, and match confidence
- Verifies matched LEI string matches target exact LEI
- Proportion of valid LEI entities successfully resolved • target: 0.98 • range: 0-1
- Benchmark: EntityRes-Eval
- Resolution Recall target: 0.98
- 1 public reference case
- Python execution harness
- Python sandbox
View technical recipe
Configured tools
- Llama Index · Required
- LlamaIndex · Optional
- Jimdo · Optional
Evaluation contract
- exact_lei_match · Weight 1
- resolution_recall · Weight 1
Recipe state
This is a preview. The configuration can change before the evaluation recipe is locked.