Cost mode:

Category: Topic Organization & Clustering · Rail: absolute · Typical I/O: 3788→5853 tokens

Models

Frontier on this task: Gemini 3.5 Flash at 8.98 / 10. Quality bar at 90%: 8.08.

point-estimate floor (CI low) · upper CI (less certain) · Bars sorted by blended cost; best-value model first. Greyed rows are MEDIUM+ models whose point estimate clears the bar but whose CI low does not.

ModelQuality scoreCI lowCost / 1k runsvs best value
Tencent Hy38.24 / 107.96$0.83best value
Gemini 3.5 Flash8.98 / 108.76$21.4726x more expensive
Moonshot Kimi K38.48 / 108.16$97.54117x more expensive
Claude Sonnet 57.20 / 106.97$9.7412x more expensive
Gemini 3.5 Flash Lite7.07 / 106.79$1.802.2x more expensive
GPT-5.6 Terra7.01 / 106.57$7.068.5x more expensive
MiniMax M37.91 / 107.49$1.311.6x more expensive
Qwen 3.7 Plus7.90 / 107.50$11.1013x more expensive
Thinking Machines Inkling Small7.79 / 107.51$7.979.6x more expensive
Thinking Machines Inkling8.01 / 107.71$24.5129x more expensive

Cost breakdown

ModelQualityConfidenceCost / 1k runsOverpayMode
Tencent Hy3 OpenRouter8.24 / 10 CI [7.96, 8.52]HIGH$0.83best valuebatch
Gemini 3.5 Flash best Gemini8.98 / 10 CI [8.76, 9.21]HIGH$21.4726xbatch
Moonshot Kimi K3 Moonshot AI8.48 / 10 CI [8.16, 8.81]MEDIUM$97.54117xbatch

Overpay shows how much more you pay than the best-value model that clears the quality bar (marked ★) — the best-value good-enough option. "16x" means you overpay 16× — 16× that reference for no quality benefit above the bar. Typical call shape for this task: 3788 input tokens → 5853 output tokens, EMA-tracked from production traffic. Cost is the observed, all-in $ per 1,000 task runs: each model's own measured usage on this task — output verbosity, thinking/reasoning tokens, cache reads and writes, and the spend on its billed failures — priced at current list rates and adjusted by the billing overhead we actually reconcile against provider invoices. Models that answer tersely cost what they actually cost; models that think at length pay for it. Not comparable to providers' advertised $/1M list rates — this is what running the task costs, not a per-token price.

Evaluation rubric

Judge dependency ordering, narrative coherence, progression, local transitions, reader orientation, and use of every topic exactly once. Identifier completeness is deterministic.

Prompt templates

The system + user template pair used for this task.

TOPIC_SEQUENCE_SYSTEM_PROMPT + TOPIC_SEQUENCE_USER_PROMPT (300 calls in window)

System prompt

You are an expert editor specializing in organizing research reports for optimal readability and narrative flow.

Your task is to determine the best sequence for presenting a set of topics in a comprehensive research report. Consider:

1. **Logical Flow**: Topics that provide context or background should come before more specific analysis
2. **Building Complexity**: Start with foundational topics, then move to more nuanced analysis
3. **Narrative Arc**: Create a compelling story that guides readers from introduction to conclusion
4. **Dependencies**: Some topics may reference or build upon information from others
5. **Reader Engagement**: Consider what order will keep readers engaged and informed

For each topic, also provide a polished section title that may differ slightly from the raw topic name to improve report cohesion.

Output a sequence that would work well for a professional research document.

## Required Output Format
Your response MUST be a single, valid JSON object conforming to this schema:
```json
{schema_json_string}
```

User prompt

Subject: {subject_name}

I have {topic_count} topics to organize into a coherent research report. Please determine the optimal sequence for presenting these topics.

Topics to sequence:
{topics_json}

Task: Analyze these topics and determine the best order for presenting them in the final report. Consider:
- What provides necessary context for other topics?
- What logical flow would help readers understand the subject?
- How can we create a compelling narrative arc?

For each topic, provide:
1. The topic_id (exactly as shown above)
2. The topic_name (exactly as shown above)

IMPORTANT: Only return the sequence order. Do NOT modify topic names or add numbering - the system handles that automatically.

The required JSON output schema is provided in the system prompt.