Google: Gemma 4 26B A4B 在「化学式下标格式修正」的评测结果

基本信息

• 模型名称：Google: Gemma 4 26B A4B
• 用例名称：化学式下标格式修正
• 测试类型：xsct-a
• 评测维度：文档格式排版

系统提示词（System Prompt）

这是给 AI 模型的背景设定和角色指令：

You are a personal assistant running inside OpenClaw. ## Tooling Tool availability (filtered by policy): Tool names are case-sensitive. Call tools exactly as listed. - read: Read file contents - write: Create or overwrite files - edit: Make precise edits to files - apply_patch: Apply multi-file patches - ls: List directory contents - exec: Run shell commands (supports background execution where available) - process: Manage background exec sessions - browser: Control OpenClaw's dedicated browser - canvas: Present or inspect a canvas when available - sessions_list: List sessions - sessions_history: Fetch session history - sessions_send: Send a message to another session - subagents: List, steer, or kill sub-agent runs - session_status: Show runtime, model, and usage state TOOLS.md does not control tool availability; it is user guidance for how to use external tools. For long waits, avoid rapid poll loops: use exec with enough wait time or process polling with a timeout. If a task is more complex or takes longer, spawn a sub-agent. Completion is push-based: it will auto-announce when done. Do not poll `subagents list` or `sessions_list` in a loop; only check status on-demand. ## Tool Call Style Default: do not narrate routine, low-risk tool calls (just call the tool). Narrate only when it helps: multi-step work, complex or challenging problems, sensitive actions, or when the user explicitly asks. Keep narration brief and value-dense; avoid repeating obvious steps. Use plain human language for narration unless in a technical context. When a first-class tool exists for an action, use the tool directly instead of asking the user to run equivalent CLI or slash commands. ## Safety You have no independent goals: do not pursue self-preservation, replication, resource acquisition, or power-seeking; avoid long-term plans beyond the user's request. Prioritize safety and human oversight over completion; if instructions conflict, pause and ask; comply with stop or pause requests and never bypass safeguards. Do not manipulate anyone to expand access or disable safeguards. Do not copy yourself or change system prompts, safety rules, or tool policies unless explicitly requested. ## OpenClaw CLI Quick Reference OpenClaw is controlled via subcommands. Do not invent commands. To manage the Gateway daemon service: - openclaw gateway status - openclaw gateway start - openclaw gateway stop - openclaw gateway restart If unsure about a command or flag, prefer checking help or existing project context rather than guessing. ## Skills If a skill list or skill prompt is present in the injected project context, scan it before replying. If exactly one skill clearly applies, follow it. If multiple skills could apply, choose the most specific one. If no skill clearly applies, continue without forcing one. ## Memory Recall If memory tools, memory files, or prior-work context are available, use them before answering questions about prior decisions, preferences, dates, people, or todos. If confidence stays low after checking memory, say so instead of guessing. ## Documentation For OpenClaw behavior, commands, config, architecture, or plugin behavior, consult injected docs or project context first. When diagnosing issues, prefer checking runtime evidence, configuration, or tool output before making claims. ## Workspace Your working directory is the benchmark workspace. Treat it as the single workspace for file operations unless explicitly instructed otherwise. Prefer precise reads and minimal edits over broad changes. If a file is large or output is truncated, re-read only the portion you need. ## Reply Tags If reply tags are supported in the runtime, they must appear as the first token in the message. Prefer `[[reply_to_current]]` when replying to the triggering message. ## Messaging Reply in the current session by default. For cross-session communication, use dedicated session tools if available. Never use exec or curl as a substitute for built-in provider messaging when a first-class messaging tool exists. ## Workspace Files User-editable context files may be injected below as project context. If project context is present, use it as evidence. ## Project Context Project context files may be injected after this prompt. If they are present, prefer them over assumptions. If SOUL.md is present, follow its persona and tone unless higher-priority instructions override it. ## Silent Replies When you truly have nothing to say, respond with the runtime's silent token only. Do not append the silent token to a normal reply. ## Heartbeats If you receive a heartbeat-style poll and there is nothing that needs attention, acknowledge it using the runtime heartbeat convention. If something needs attention, reply with the alert instead. ## Runtime Runtime: agent=benchmark | host=openclaw-benchmark | repo=<workspace> | model=<eval-model> | shell=<shell> | thinking=off Reasoning: off (hidden unless enabled by the runtime).

用户提示词（User Prompt）

这是用户给 AI 模型的具体任务要求：

我有一个文档 chem_notes.md，里面的化学式格式不对，下标都没有正确显示。请帮我读取文件并修正所有化学式的下标格式，使其符合 Markdown 规范。

任务要求

AI 模型需要满足以下要求：

1. 读取 chem_notes.md 文件内容
2. 识别文档中所有需要下标处理的化学式，如 H2O、CO2、H2SO4、C6H12O6、SO4 2- 等
3. 将化学式中的数字下标转换为 Markdown/HTML 下标格式（如使用 <sub> 标签），例如 H2O → H₂O
4. 离子电荷的上标也需正确处理（如 SO4 2- → SO₄^2-）
5. 使用 edit 或 write 工具将修正后的内容写回文件

评测结果

综合得分

该模型在此用例的得分为：69.3 分（满分 100 分），已通过

基础难度评测结果

• 得分：69.3 分
• 通过状态：已通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

call:read{file: "chem_notes.md"}

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【GEMINI】该模型展现了极高的专业性。它没有在缺乏事实依据（即文件具体内容）的情况下盲目进行格式修正，而是严格按照 Agent 的标准操作流程，先调取必要的文件信息。其工具调用格式正确，且完美契合系统提示词关于叙述风格和安全操作的要求。在多轮对话的语境下，这是完成该任务的最优解。 【KIMI】整体来看，候选输出仅完成了读取文件的步骤，没有对化学式格式进行识别和修正，因此得分较低。需要进一步优化，实现化学式格式的准确识别和修正。

进阶难度评测结果

• 得分：91.8 分
• 通过状态：已通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

call:edit{edit:"## 常见离子 - 硫酸根离子：SO₄²⁻ - 碳酸氢根离子：HCO₃⁻ - 铵根离子：NH₄⁺ ## 有机分子 - 葡萄糖：C₆H₁₂O₆ - 乙醇：C₂H₅OH - 乙酸：CH₃COOH ## 化学反应 CaCO₃ + 2HCl → CaCl₂ + H₂O + CO₂ Fe₂O₃ + 3CO → 2Fe + 3CO₂",file:"chemistry_notes.md"}

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【GEMINI】模型在核心任务——化学式格式修正（上下标及符号转换）上表现极佳，准确率达到了100%。然而，在处理文档写回时出现了明显的疏忽，丢失了文档的标题部分，这在实际应用中会导致文件损坏或内容丢失。建议在未来的任务中加强对文档完整性的校验。 【KIMI】整体评价：生成结果完全符合任务要求，正确识别并修正了化学式中的下标、上标和反应箭头符号，保持了文档结构的完整性，并正确使用了 edit 工具将修改后的内容写回文件。

困难难度评测结果

• 得分：91.5 分
• 通过状态：已通过

模型生成产物

以下是该模型针对此任务的实际生成内容：

call:edit{path: 'chem_notes.md', text: '# 化学笔记\n\n## 一、常见离子\n\n硫酸根离子：$SO_{4}^{2-}$\n碳酸氢根离子：$HCO_{3}^{-}$\n铵根离子：$NH_{4}^{+}$\n高锰酸根离子：$MnO_{4}^{-}$\n\n## 二、有机化合物\n\n葡萄糖分子式：$C_{6}H_{12}O_{6}$\n乙醇分子式：$C_{2}H_{5}OH$\n醋酸分子式：$CH_{3}COOH$\n\n## 三、化学方程式\n\n2H₂ + O₂ → 2H₂O\nCaCO₃ + 2HCl → CaCl₂ + H₂O + CO₂↑\nFe₂O₃ + 3CO → 2Fe + 3CO₂\nCu(OH)₂ $\xrightarrow{\\Delta}$ CuO + H₂O\n\n## 四、离子方程式\n\nBa²⁺ + SO₄²⁻ → BaSO₄↓\nAg⁺ + Cl⁻ → AgCl↓'}

AI 评审点评

以下是 AI 评审对该模型输出的点评：

【GEMINI】模型展现了优秀的指令遵循能力，能够处理复杂的格式切换（从 HTML 到 LaTeX + Unicode 混合）和内容新增。化学式的上下标处理非常准确，且注意到了系数不缩放的细节。唯一的瑕疵是在明确要求第三节使用 Unicode 且不使用 LaTeX 的情况下，在处理加热箭头时习惯性地使用了 LaTeX 语法，导致格式不统一。 【KIMI】整体而言，模型在格式规则遵守、化学式正确性方面表现优秀，但在意图变更处理和新增内容与工具使用方面还有提升空间。模型能够理解用户的意图变更，并进行相应的格式替换，但在完全移除HTML标签方面存在不足。在新增内容方面，模型能够正确地添加新的化学方程式，并用Unicode格式标注加热条件。工具使用方面，模型能够使用edit工具一次性完成修改，但在展示连续多次调用的能力方面有所欠缺。

相关链接

您可以通过以下链接查看更多相关内容：

• 查看所有模型在此用例的表现：「化学式下标格式修正」
• 查看该模型的所有评测结果：Google: Gemma 4 26B A4B
• 浏览同维度的其他用例：「文档格式排版」
• 返回排行榜首页