Explode salaryByCurrency into rows, and your salary corpus gets bigger without gaining another observation. The row counter looks delighted. Your evaluation deserves less enthusiasm.
The catch: this is a verdict about schema design, not a measured improvement in retrieval or model quality. Our grouping key is a proposed ingestion policy, not a guaranteed source identifier.
Lab note 069: which fields does an LLM need to compare salary benchmarks without counting currency representations as fresh evidence?
What's the retrieval unit?
You're flattening salary data for retrieval, and the nested currency object looks like useful material for separate examples.
For this salary Actor, salaryByCurrency includes all ten benchmark currencies; the top-level percentile fields use the selected salaryCurrency , or the country's currency when that input is empty.
Currency representations of a salary benchmark are views of the same evidence, not independent salary observations.
Our task is narrow: let an LLM compare…