Papers › ACES: Translation Accuracy Challenge Sets for Evaluating Machine Translation Metrics

ACES: Translation Accuracy Challenge Sets for Evaluating Machine Translation Metrics

27 Oct 2022arXiv:2210.15615archive 2025-07-28

Chantal Amrhein, Nikita Moghe, Liane Guillou

As machine translation (MT) metrics improve their correlation with human judgement every year, it is crucial to understand the limitations of such metrics at the segment level. Specifically, it is important to investigate metric behaviour when facing accuracy errors in MT because these can have dangerous consequences in certain contexts (e.g., legal, medical). We curate ACES, a translation accuracy challenge set, consisting of 68 phenomena ranging from simple perturbations at the word/character level to more complex errors based on discourse and real-world knowledge. We use ACES to evaluate a wide range of MT metrics including the submissions to the WMT 2022 metrics shared task and perform several analyses leading to general recommendations for metric developers. We recommend: a) combining metrics with different strengths, b) developing metrics that give more weight to the source and less to surface-level overlap with the reference and c) explicitly modelling additional language-specific information beyond what is available via multilingual embeddings.

PaperPDFCodeCode Syntology ran

In Syntology View this paper on Syntology, its page in Syntology's graph. That page adds which of its functions are also present in other papers' code Syntology holds, with dates, and its dated run record as JSON and a README badge. It also lists the repositories linked to the paper, the abstract and the calls for agents.

Open this paper in Syntology's Atlas, the map of the papers in Syntology's graph and their citations.

For agents, on Syntology's MCP service (how to connect):

Code

Syntology 2 code samples harvested from 1 repository linked to this paper: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 2 samples from 1 repository, 2 ran (1 with no instrument failure; 1 where Syntology's instrument failed). The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

Levels written on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.

edinburghnlp/aces officialmentioned in papermentioned on GitHubSyntology: 2 samples, 2 ran (1 instrument-failed) · 0 unverified report

Repository list and official/mentioned flags are the archive's, frozen 2025-07-28. Reachability, where shown, is from one Syntology probe window (2026-09-16 to 2026-09-18); repositories not probed show nothing. GitHub stars are not tracked.

Code Syntology ran Syntology

2 samples harvested: 2 ran (of which 0 constructed an object rather than computing a result; 1 with no instrument failure: 1 honoured, 0 violated, 0 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page has not changed since , the first build that kept a record date for it; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · our draft was wrong

Licence: 2 of the 2 samples are pointer only, meaning Syntology does not serve that copy's text. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from edinburghnlp/aces. “Ran” means the sample executed on a synthesized input. It does not mean the output is correct, and nothing here reproduces the paper's results. A line beginning “fixture:” under a sample that ran gives the arguments Syntology's fixture called the sample with, each as name:type/rank/element kind (? where none was recorded), and the type of what the fixture's run returned, exactly as the harness recorded them; the arguments and the returned type were recorded by two separate runs of the same fixture. No output value is shown, and a returned type says nothing about whether the output was right. “Level recorded” gives the UTC date when Syntology's graph wrote the sample's verification level, not when the code executed; where the level was written before Syntology's graph kept that date, the row says “level recorded, date not recorded”. “Honoured” and “violated” refer to a contract Syntology drafted from the code itself. “Our draft was wrong” and “the contract check could not run” are failures of Syntology's instrument, not of the code: the sample ran on Syntology's synthesized input, and then the drafted contract did not describe it, or the check itself raised an error (RAISES), lacked a dependency (DEP_MISSING) or ran out of time (TIMEOUT); hover the label for which. A metamorphic tier, where shown, is evidence of the output's shape, not that the sample implements the method.

Each sample ends with its code_sha256. A sample's code_sha256 is Syntology's identity for that exact code. It is printed in full (16 hexadecimal characters for every sample in this build), and get_code(code_sha256="…") takes it exactly as printed. An agent calls it on Syntology's MCP service (how to connect); click an identity to copy that call.

Repository labels, per sample. official repository: The archive marks this repository official for the paper. named in the paper: The archive records that the paper mentions this repository; it is not marked official. community (archive-listed): In the archive's code links for this paper, not marked official and not recorded as mentioned in the paper. found in paper text by Syntology: Syntology found this repository in the paper's own text; whether it is the authors' implementation is not asserted. community: Not in the archive's code links for this paper; a community repository Syntology harvested. Samples are grouped by repository: a repository marked official first, then by how directly the repository is tied to the paper, then in the archive's order; never by how many ran. Licence labels name the repository's licence as recorded at harvest. “Pointer only” means Syntology does not serve that copy's text, for one of six reasons: no licence file was found; the licence was not identified; the licence is recorded as permissive but that copy's record is not marked cleared; the licence is outside the permissive list Syntology serves text under (MIT, Apache-2.0, BSD and similar); this paper's copy was not located, so its licence is not recorded; or this paper's copy is cleared, but the stored copy of the same code that Syntology serves is not. Some licences outside that list permit redistribution, such as WTFPL, and GPL-3.0 under its conditions; they are simply not on the list. Hover a licence label for the reason. File links open the file on GitHub at the default branch, which may have changed since the harvest.

edinburghnlp/aces official repository 2 samples, 2 ran (1 instrument-failed) · 0 unverified
comp_aces_score aces/cli/evaluate.py ran · honoured contract no licence file found · pointer only · bbcfcf7cdfa562ac · report fixture: signature overview_results:dict/0/? · returned float64 · level recorded 2026-09-22
comp_corr aces/cli/evaluate.py ran · our draft was wrong no licence file found · pointer only · 413ea7f78d43e011 · report fixture: signature good_scores:Series/1/float, incorrect_scores:Series/1/float · returned float64 · level recorded 2026-09-22

Tasks

Machine TranslationTranslationWorld Knowledge

Datasets

Introduced by this paper, per the archive.

ACES

Results from the paper archive 2025-07-28

TaskDatasetModelMetricValueRank at snapshotLeaderboardReport
Machine Translation ACES HWTSC-Teacher-Sim Score 19.97 #1 of 21 Archive leaderboard report
Machine Translation ACES MS-COMET-22 Score 19.89 #2 of 21 Archive leaderboard report
Machine Translation ACES MS-COMET-QE-22 Score 19.76 #3 of 21 Archive leaderboard report
Machine Translation ACES KG-BERTScore Score 17.28 #4 of 21 Archive leaderboard report
Machine Translation ACES metricx_xl_DA_2019 Score 17.17 #5 of 21 Archive leaderboard report
Machine Translation ACES COMET-QE Score 16.8 #6 of 21 Archive leaderboard report
Machine Translation ACES COMET-22 Score 16.31 #7 of 21 Archive leaderboard report
Machine Translation ACES UniTE-src Score 15.68 #8 of 21 Archive leaderboard report
Machine Translation ACES UniTE-ref Score 15.38 #9 of 21 Archive leaderboard report
Machine Translation ACES metricx_xxl_DA_2019 Score 15.24 #10 of 21 Archive leaderboard report
Machine Translation ACES UniTE Score 14.76 #11 of 21 Archive leaderboard report
Machine Translation ACES Cross-QE Score 14.07 #12 of 21 Archive leaderboard report
Machine Translation ACES chrF Score 13.57 #13 of 21 Archive leaderboard report
Machine Translation ACES metricx_xl_MQM_2020 Score 13.08 #14 of 21 Archive leaderboard report
Machine Translation ACES COMET-20 Score 12.06 #15 of 21 Archive leaderboard report
Machine Translation ACES BLEURT-20 Score 11.9 #16 of 21 Archive leaderboard report
Machine Translation ACES YiSi-1 Score 11.38 #17 of 21 Archive leaderboard report
Machine Translation ACES BERTScore Score 10.47 #18 of 21 Archive leaderboard report
Machine Translation ACES BLEU Score -3.13 #19 of 21 Archive leaderboard report
Machine Translation ACES f101spBLEU Score -0.33 #20 of 21 Archive leaderboard report
Machine Translation ACES f200spBLEU Score -0.18 #21 of 21 Archive leaderboard report

Ranks are positions in the archive's leaderboards as they stood at the 2025-07-28 snapshot. Results published since then are not among these rows, so a rank here is not a current standing.

Report a problem or propose a change · a person checks every report against the paper or source before anything changes; decisions are listed on /corrections