Back to demo

Model evaluation

Dev_Beam comparison · November 1, 2026

What this measures: model-judged usefulness of proposed responses to fictional support scenarios. It is not a measure of eligibility accuracy, live app performance, or overall model superiority.

Method

Eight models were compared across 20 scenario runs each (16 distinct case IDs, with four repeated). Each selected response received a 0–10 usefulness score from an LLM. Judges differ between models; results remain pending human review. A separate human/LLM comparison covered 12 selected responses, not a representative sample.

Completion after documented retries was 20/20 for each model. The table shows first-attempt completion separately. Response time is the elapsed time around one model invocation, including the API round trip and response handling; it is not isolated model compute time. The mean uses the selected completed response for each of 20 runs. It excludes time spent on earlier failed attempts and does not measure the full app workflow. Cost is an estimate for generation attempts; it excludes judge costs and may be unavailable.

ModelLLM score / 10First attemptMean response time (s)Estimated USD / run
Beam7.9520/202.95$0.001870
DeepSeek8.3020/2013.16$0.002132
GLM8.3017/2040.93$0.001856
Qwen7.9520/209.72$0.000899
Kimi7.9017/2091.71Not available
MiniMax7.9520/2059.52$0.000856
Gemma7.7520/208.62$0.000170
GPT-OSS7.1020/2012.42$0.000324
Rounded values; see the JSON for unrounded values. Inference and judge configurations differed between models.

Response time

Beam: 2.95 seconds on average across 20 completed responses (20/20 completed on the first attempt). These were requests for fictional support-planning scenarios, not the multi-step app flow. Other models’ means and first-attempt completion counts are in the table above. GLM and Kimi each had three initial failures that were retried; their averages cover only the selected successful responses and omit earlier waiting time. Provider, execution settings, parallelism and timing differed, so the numbers are not a controlled hardware-speed benchmark.

Limitations

Small score differences should not be treated as statistically significant.

Files

Case-level results (CSV, 160 rows) · Aggregated data and method (JSON) · Detailed report (Japanese)

Charts

Average usefulness scores · Score and response time · Score and estimated cost