Paper Metadata Retrieval
Find the single paper satisfying both a substantive research need and its source-metadata constraints.
- Domain
constrained paper search- Primary focus
Paper Metadata Retrieval- Primary metric
Accuracy@1
On this page
Runtime and requirements
- Agent budget:
2 hours - Compute:
16CPUs,32 GiBRAM,100 GiBstorage;0GPU(s)
Build: 1,800 seconds. Eight sequential evaluation invocations: 30 seconds each including startup, APIs and output. No training or fine-tuning. Only documented OpenRouter/Jina resources; no external search or answer collections.
Public input and output contract
Inputs
/task/data/corpus.sqlite holds 70,000 papers and metadata. Public query/answer JSONL is under /task/data/validation/. Requests contain query_id and query. Distinguish first submission from publication dates and institution location from author citizenship.
Outputs
Submit executable /app/build.sh --corpus /task/data/corpus.sqlite --index-dir DIR and /app/run.sh --index-dir DIR --queries PATH --output PATH --top-k 1, plus dependencies under /app. Build may start a persistent service. Honor writable index/output/TMPDIR paths under the non-root read-only-code verifier.
Return exactly one doc_id/finite numeric score item in results, preserving query_id. A merely related topic or hypothetically adaptable method is insufficient.
Evaluation
Reward is mean Accuracy@1 across all eight requests. Timeouts zero only their query; failed build, other command failure, invalid output or resource/integrity failure zeros the entire submission.
Final reward requires a healthy, accepting independent trajectory and submission integrity audit. Audit failures are reported separately from retrieval quality and cannot produce positive credit.
See the full instructions, task documentation and runtime configuration for the complete contract at the synchronized benchmark revision.