Build a Public Tender Bid Rigging and Officer Lineage Investigator
Analyze public contracting releases alongside corporate registry records to detect common executive officers across rival bidders. Compile structured case files with corporate relationship evidence.
What you are building
The core problem, expected build, and operating context for this challenge.
Analyze public contracting releases alongside corporate registry records to detect common executive officers across rival bidders. Compile structured case files with corporate relationship evidence.
Anti-corruption procurement analyst
Extract bidding supplier corporate identifiers and officer rosters from OCDS tender releases.
Query simulated GLEIF parent-child and officer relationship records for each bidding entity.
Identify undisclosed overlapping directors, legal representatives, or parent affiliates participating in the same tender lot.
Formulate a chronological case brief summarizing common officer appointment dates and tender submission timestamps.
Multi-column procurement review console showing tender bidder lists, shared officer lineages, and case timeline exports.
Create synthetic OCDS tender documents alongside mock GLEIF relationship records linking corporate directors and parent LEIs. Starter examples below are synthetic. They are not downloaded records.
GLEIF API Leverages the GLEIF corporate structure search concepts to link legal entities through direct parent and officer records.
dspy, pandas, pydantic. DSPy optimizes prompt pipelines to reliably extract subtle entity relationship overlaps into structured case summaries. Requires local or remote LLM compatible with DSPy module execution for structured relation extraction.
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.
Correlates distinct legal entities submitting bids against the same tender award lot.
Flags overlapping officers or direct parents shared across rival bidders using GLEIF-style entity links.
Assembles an evidence summary linking officer names, appointment dates, and tender submission IDs.
```json [ { "input": { "ocid": "ocds-tender-8831", "bidders": [ { "lei": "5493006MHB84DD0ZWV18", "name": "Alpha Engineering" }, { "lei": "549300ABCD0000123456", "name": "Beta Infra Corp" } ], "gleif_officers": [ { "lei": "5493006MHB84DD0ZWV18", "officer_name": "Elena Rostova", "role": "Director" }, { "lei": "549300ABCD0000123456", "officer_name": "Elena Rostova", "role": "Managing Officer" } ] }, "expected_output": { "conflict_flag": true, "shared_officers": [ { "name": "Elena Rostova", "entities": [ "Alpha Engineering", "Beta Infra Corp" ] } ], "recommendation": "Escalate to procurement integrity review for potential horizontal collusion." } }, { "input": { "ocid": "ocds-tender-8832", "bidders": [ { "lei": "54930011112222333344", "name": "Green Power Ltd" } ], "gleif_officers": [ { "lei": "54930011112222333344", "officer_name": "Marcus Vance", "role": "Director" } ] }, "expected_output": { "conflict_flag": false, "shared_officers": [], "recommendation": "Standard evaluation proceeds; no common officer detected." } } ] ```
Processes synthetic corporate records only; no live enterprise databases or regulatory actions are triggered. Use mock external writes. Require human review before any real deployment.
Participation guide
Processes synthetic corporate records only; no live enterprise databases or regulatory actions are triggered. Use mock external writes and human review.
How work is evaluated
Correlates distinct legal entities submitting bids against the same tender award lot. Flags overlapping officers or direct parents shared across rival bidders using GLEIF-style entity links. Assembles an evidence summary linking officer names, appointment dates, and tender submission IDs.
Runnable source, pinned dependencies, setup commands, working interface, example outputs, recorded demo, tests, and action logs.
Challenge datasets
Public datasets, plus the private datasets you have access to.
How submissions are scored
These dimensions define what the evaluator checks and which criteria separate a passable run from a strong one.
Complete workflow
Extract bidding supplier corporate identifiers and officer rosters from OCDS tender releases. Query simulated GLEIF parent-child and officer relationship records for each bidding entity. Identify undisclosed overlapping directors, legal representatives, or parent affiliates participating in the same tender lot. Formulate a chronological case brief summarizing common officer appointment dates and tender submission timestamps.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Correctness and evidence
Correlates distinct legal entities submitting bids against the same tender award lot. Flags overlapping officers or direct parents shared across rival bidders using GLEIF-style entity links. Assembles an evidence summary linking officer names, appointment dates, and tender submission IDs.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Review interface
Multi-column procurement review console showing tender bidder lists, shared officer lineages, and case timeline exports.
Missing or incorrect.
Partly complete, with documented gaps.
Complete, with reproducible evidence.
Safe execution
Processes synthetic corporate records only; no live enterprise databases or regulatory actions are triggered.
This dimension contributes its full weight only when the submission satisfies the requirement. Partial credit is not awarded.
What you should walk away with
Extract bidding supplier corporate identifiers and officer rosters from OCDS tender releases.
Query simulated GLEIF parent-child and officer relationship records for each bidding entity.
Identify undisclosed overlapping directors, legal representatives, or parent affiliates participating in the same tender lot.
Formulate a chronological case brief summarizing common officer appointment dates and tender submission timestamps.
Reference links and supporting material
Create synthetic OCDS tender documents alongside mock GLEIF relationship records linking corporate directors and parent LEIs. Supplied starter examples are synthetic, not source extracts.
Challenge setup
Configuration summary for this challenge.
Challenge input
Input details are not configured.
DSPy
Prompt and LM program optimization framework.
Evaluated output
No output checks are configured.
- Extract bidding supplier corporate identifiers and officer rosters from OCDS tender releases. Query simulat...
- Correlates distinct legal entities submitting bids against the same tender award lot. Flags overlapping off...
- Multi-column procurement review console showing tender bidder lists, shared officer lineages, and case time...
- 2 public reference cases
- 3 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
- DSPy · Optional
- DSPy · Optional
- DSPy · 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.