Skip to content
AAA.win
EN
EnglishEN中文ZH日本語JAEspañolES
SearchSubmit a tool
Menu

Japanese Business Email Politeness Rewrite

Can the agent make Japanese business email polite and natural without changing facts?

日本語Writingunnatural_japanese
Preview evidencemaa-preview-002

Full task input

Rewrite a direct Japanese follow-up email into concise business Japanese.

Scoring rubric

Must preserve the same deadline and meeting context while avoiding over-humble or blunt language.
Primary risk
unnatural_japanese
Temperature
0.2
Tools
Disabled
Web browsing
Disabled
Memory
Disabled

Agent prompt summary

Rewrite a direct Japanese follow-up email into concise business Japanese.

Rubric summary

Must preserve the same deadline and meeting context while avoiding over-humble or blunt language.

Task leaderboard

OpenAI Main850% critical
Claude Main850% critical
MiniMax Main830% critical
Kimi Main8133% critical
Gemini Main800% critical
Qwen Main800% critical
Mistral Main800% critical
GLM Main800% critical
Hunyuan Main800% critical
Doubao Main800% critical
Grok Main7933% critical
Llama Main790% critical
Perplexity Main7933% critical
ERNIE Main790% critical
DeepSeek Main770% critical
Cohere Main770% critical
Yi Main770% critical
Phi Main7333% critical

Common failure tags

unsupported_claimliteral_translationunnatural_japaneseweak_ctamissing_fieldmissed_dependency

Sample outputs and scoring notes

OpenAI Main currently leads this task. When reading samples, focus on task completion, whether the output respects business boundaries such as unnatural_japanese, and whether the structure can move into a workflow. The most visible failure tag is unsupported_claim.

OpenAI Main

maa-preview-002.japanese-business-email-rewrite.openai-main.02

Preview
Batch: maa-preview-002Model version: Not measuredTemperature: 0.2Cost: $0.0246Latency: Not measuredHuman review: Not reviewed

Raw output (untruncated)

Preview seed output. Replace with exact model output for real evaluations.
Valid JSONRequired fields presentNo critical failure
Run score88
task success
5/5
language fit
5/5
instruction following
4/5
business safety
4/5
output reliability
4/5

Review note: Synthetic preview score generated from deterministic seed data.

Phi Main

maa-preview-002.japanese-business-email-rewrite.phi-main.01

Preview
Batch: maa-preview-002Model version: Not measuredTemperature: 0.2Cost: $0.0054Latency: Not measuredHuman review: Not reviewed

Raw output (untruncated)

Preview seed output. Replace with exact model output for real evaluations.
Invalid JSONRequired fields missingCritical failure
unnatural_japaneseinvalid_json
Run score64
task success
4/5
language fit
4/5
instruction following
2/5
business safety
3/5
output reliability
3/5

Review note: Synthetic preview score generated from deterministic seed data.

Downloads use the same run objects as this page.

Version · v4.3.6-indexnow-delivery-verified

Latest releases

IndexNow production delivery verification

Verified production IndexNow receipt with a new key: Microsoft's external proof returned HTTP 200, single-URL GET and POST both returned HTTP 200, and eight batches covering 386 canonical URLs each returned HTTP 200 with zero retries. A second run found the inventory unchanged and sent no request.

IndexNow proof-origin protocol fix

Production Bing validation exposed HTTP 500 at the external root proof because TLS termination was followed by an internal rewrite using the wrong protocol. This release corrects that rewrite boundary, but remains unverified until the external proof returns HTTP 200, the automatic submission runs, a later canary returns HTTP 200, and the idempotent rerun passes.

IndexNow root-proof request compatibility

After v4.3.3, the exact root-level {key}.txt proof returned HTTP 200, but a full request carrying keyLocation still returned HTTP 403; a minimal homepage request with the same production key and no keyLocation returned HTTP 202. This release omits that field, while the automatic full run and idempotent rerun remain deployment checks.

View all releases