SimInter: Evidence-Grounded User Simulation with Interview-Based Profile Enrichment for Conversational Recommender Systems

An agent looks good in demos, but you cannot tell which product tasks it fails.

What you would change

Use the study's evaluation idea to inspect a small set of tasks with human-checked answers.

Use the study's evaluation idea to inspect a small set of tasks with human-checked answers.

Compare against

Your current evaluator and a manually reviewed reference set.

1. Locate the paper's implementation and check its license, model support, data needs, and hardware requirements. Stop here if you cannot obtain the required artifacts.
2. Save a small set of representative product tasks and expected outcomes. Keep evaluation tasks out of any training or tuning, and choose quality and cost limits before running.
3. Run the baseline and the proposed change on identical inputs. Keep other settings fixed and repeat paired runs to expose variation.
4. Save per-task outputs, failures, timings, and all usage costs. Review regressions before expanding the test.

What to measure

Agreement with human review, missed failures, false alarms, and evaluation cost per task.

When to keep it

Keep the change only if it meets your preselected quality and latency limits and improves the metric you care about after setup and operating costs. Otherwise retain the baseline. This is an exploration plan, not a validated recommendation.

recommendation

test

research area

agent evaluation

technical change

Interview-enriched LLM user simulation for CRS evaluation

published

2026-10-13

The method runs entirely on LLM API calls suitable for constrained infrastructure and shows a statistically significant, human-validated improvement in simulator fidelity, but its evidence is limited to one domain and dataset, so workload-specific validation is required before production reliance.

1. claim 01Paperraft inference
   Read the brief interpretation

   SimInter replaces user simulators conditioned only on ratings, demographics, and static profiles by enriching profiles through synthetic LLM interviews grounded in historical conversational evidence, with a turn-level audit agent flagging fabrication and stereotyping. The cost is additional LLM inference for interview generation and auditing per simulated user, plus pipeline complexity; it is feasible on API access or a single GPU, but the paper validates only movie recommendation on ReDial, so transfer to other domains is unverified. After adoption, the main failure mode is residual fabricated or stereotyped attributes passing the audit (about 5.7% of claims unsupported and 4.8% auditor disagreement), which can bias downstream recommender evaluation.

   This is a Paperraft inference. It is not pinned to a verified PDF passage.

   Inspect the source
2. claim 02Paperraft inference

   On 100 matched ReDial users, enriched profiles raise expressed preference-aspect diversity versus a statistics-only baseline (filtered aspect entropy 1.619 vs 0.859; paired d=0.96, Holm-adjusted p<0.001), persisting across two recommenders and two judges (+0.28 to +0.56 nats); humans find 94.3% of enriched attributes supported or partially supported and agree with 95.2% of auditor filtering decisions.

   This is a Paperraft inference. It is not pinned to a verified PDF passage.

   Inspect the source