WAT

The Workshop on Asian Translation

Evaluation Results

BLEU

#	Team	Task	Date/Time	DataID	BLEU										Method	Other Resources	System Description
#	Team	Task	Date/Time	DataID	juman	kytea	mecab	moses- tokenizer	stanford- segmenter- ctb	stanford- segmenter- pku	indic- tokenizer	unuse	myseg	kmseg	Method	Other Resources	System Description
1	NTT	TDDCTXTja-en	2019/07/22 14:39:28	2800	-	-	-	55.26	-	-	-	-	-	-	NMT	No	Transformer Big Single
2	sarah	TDDCTXTja-en	2019/07/22 16:19:17	2808	-	-	-	58.38	-	-	-	-	-	-	NMT	No	Transformer, ensemble of 4 models
3	NTT	TDDCTXTja-en	2019/07/22 16:19:35	2809	-	-	-	58.91	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data
4	sarah	TDDCTXTja-en	2019/07/22 16:24:03	2812	-	-	-	54.84	-	-	-	-	-	-	NMT	No	Transformer, single model
5	NTT	TDDCTXTja-en	2019/07/23 13:04:46	2852	-	-	-	60.48	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data 4 models ensemble
6	NTT	TDDCTXTja-en	2019/07/26 13:56:37	3005	-	-	-	61.19	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data R2L re-ranking 4 models ensemble
7	NICT-2	TDDCTXTja-en	2019/07/26 22:28:22	3083	-	-	-	55.28	-	-	-	-	-	-	NMT	No	Transformer, single model w/ long warm-up
8	NICT-2	TDDCTXTja-en	2019/07/26 22:30:03	3084	-	-	-	56.95	-	-	-	-	-	-	NMT	No	Transformer, ensemble of 4 models w/ long warm-up
9	geoduck	TDDCTXTja-en	2019/07/27 14:13:28	3200	-	-	-	61.38	-	-	-	-	-	-	Other	Yes	TM + NMT (a single Transformer)
10	geoduck	TDDCTXTja-en	2019/07/27 16:44:46	3217	-	-	-	51.08	-	-	-	-	-	-	Other	Yes	TM + MT (ensemble)
11	ORGANIZER	TDDCTXTja-en	2019/08/02 16:46:45	3263	-	-	-	24.11	-	-	-	-	-	-	NMT	No	baseline using OpenNMT
12	ORGANIZER	TDDCTXTja-en	2019/08/02 16:56:33	3265	-	-	-	25.37	-	-	-	-	-	-	Other	Yes	Azure Custom Translator

Notice:

This table is sorted by the leftmost segmenters. You can change the segmenter used to sort by clicking each segmenter link.

RIBES

#	Team	Task	Date/Time	DataID	RIBES										Method	Other Resources	System Description
#	Team	Task	Date/Time	DataID	juman	kytea	mecab	moses- tokenizer	stanford- segmenter- ctb	stanford- segmenter- pku	indic- tokenizer	unuse	myseg	kmseg	Method	Other Resources	System Description
1	NTT	TDDCTXTja-en	2019/07/22 14:39:28	2800	-	-	-	0.839808	-	-	-	-	-	-	NMT	No	Transformer Big Single
2	sarah	TDDCTXTja-en	2019/07/22 16:19:17	2808	-	-	-	0.865364	-	-	-	-	-	-	NMT	No	Transformer, ensemble of 4 models
3	NTT	TDDCTXTja-en	2019/07/22 16:19:35	2809	-	-	-	0.851833	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data
4	sarah	TDDCTXTja-en	2019/07/22 16:24:03	2812	-	-	-	0.845921	-	-	-	-	-	-	NMT	No	Transformer, single model
5	NTT	TDDCTXTja-en	2019/07/23 13:04:46	2852	-	-	-	0.858363	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data 4 models ensemble
6	NTT	TDDCTXTja-en	2019/07/26 13:56:37	3005	-	-	-	0.861346	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data R2L re-ranking 4 models ensemble
7	NICT-2	TDDCTXTja-en	2019/07/26 22:28:22	3083	-	-	-	0.840931	-	-	-	-	-	-	NMT	No	Transformer, single model w/ long warm-up
8	NICT-2	TDDCTXTja-en	2019/07/26 22:30:03	3084	-	-	-	0.848530	-	-	-	-	-	-	NMT	No	Transformer, ensemble of 4 models w/ long warm-up
9	geoduck	TDDCTXTja-en	2019/07/27 14:13:28	3200	-	-	-	0.850551	-	-	-	-	-	-	Other	Yes	TM + NMT (a single Transformer)
10	geoduck	TDDCTXTja-en	2019/07/27 16:44:46	3217	-	-	-	0.659190	-	-	-	-	-	-	Other	Yes	TM + MT (ensemble)
11	ORGANIZER	TDDCTXTja-en	2019/08/02 16:46:45	3263	-	-	-	0.701005	-	-	-	-	-	-	NMT	No	baseline using OpenNMT
12	ORGANIZER	TDDCTXTja-en	2019/08/02 16:56:33	3265	-	-	-	0.725205	-	-	-	-	-	-	Other	Yes	Azure Custom Translator

Notice:

This table is sorted by the leftmost segmenters. You can change the segmenter used to sort by clicking each segmenter link.

AMFM

#	Team	Task	Date/Time	DataID	AMFM										Method	Other Resources	System Description
#	Team	Task	Date/Time	DataID	unuse	unuse	unuse	unuse	unuse	unuse	unuse	unuse	unuse	unuse	Method	Other Resources	System Description
1	NTT	TDDCTXTja-en	2019/07/22 14:39:28	2800	-	-	-	0.727530	-	-	-	-	-	-	NMT	No	Transformer Big Single
2	sarah	TDDCTXTja-en	2019/07/22 16:19:17	2808	-	-	-	0.745110	-	-	-	-	-	-	NMT	No	Transformer, ensemble of 4 models
3	NTT	TDDCTXTja-en	2019/07/22 16:19:35	2809	-	-	-	0.742730	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data
4	sarah	TDDCTXTja-en	2019/07/22 16:24:03	2812	-	-	-	0.732790	-	-	-	-	-	-	NMT	No	Transformer, single model
5	NTT	TDDCTXTja-en	2019/07/23 13:04:46	2852	-	-	-	0.749680	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data 4 models ensemble
6	NTT	TDDCTXTja-en	2019/07/26 13:56:37	3005	-	-	-	0.753630	-	-	-	-	-	-	NMT	No	Transformer Big Single Fine-tuned with items data R2L re-ranking 4 models ensemble
7	NICT-2	TDDCTXTja-en	2019/07/26 22:28:22	3083	-	-	-	0.732660	-	-	-	-	-	-	NMT	No	Transformer, single model w/ long warm-up
8	NICT-2	TDDCTXTja-en	2019/07/26 22:30:03	3084	-	-	-	0.744390	-	-	-	-	-	-	NMT	No	Transformer, ensemble of 4 models w/ long warm-up
9	geoduck	TDDCTXTja-en	2019/07/27 14:13:28	3200	-	-	-	0.743820	-	-	-	-	-	-	Other	Yes	TM + NMT (a single Transformer)
10	geoduck	TDDCTXTja-en	2019/07/27 16:44:46	3217	-	-	-	0.623770	-	-	-	-	-	-	Other	Yes	TM + MT (ensemble)
11	ORGANIZER	TDDCTXTja-en	2019/08/02 16:46:45	3263	-	-	-	0.583850	-	-	-	-	-	-	NMT	No	baseline using OpenNMT
12	ORGANIZER	TDDCTXTja-en	2019/08/02 16:56:33	3265	-	-	-	0.602290	-	-	-	-	-	-	Other	Yes	Azure Custom Translator

Notice:

This table is sorted by the leftmost segmenters. You can change the segmenter used to sort by clicking each segmenter link.
Adequacy-Fluency Metrics (AMFM) is a two-dimensional automatic evaluation metric for machine translation, designed to operate at the sentence level. It is based on adequacy and fluency, to decouple semantic and syntactic components of the translation process to provide a balanced view on translation quality.
AMFM is calculated without tokenizers.
The detail of AMFM is shown on the following paper: "Adequacy–Fluency Metrics: Evaluating MT in the Continuous Space Model Framework" [pdf]. Invited Talk in WAT2015 also helps understanding [slide].

HUMAN (WAT2022)

Notice:

HUMAN (WAT2022) is the result of the Pairwise Crowdsourcing Evaluation on WAT2022.
HUMAN (WAT2022) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2021)

Notice:

HUMAN (WAT2021) is the result of the Pairwise Crowdsourcing Evaluation on WAT2021.
HUMAN (WAT2021) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2020)

Notice:

HUMAN (WAT2020) is the result of the Pairwise Crowdsourcing Evaluation on WAT2020.
HUMAN (WAT2020) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2019)

Notice:

HUMAN (WAT2019) is the result of the Pairwise Crowdsourcing Evaluation on WAT2019.
HUMAN (WAT2019) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2018)

Notice:

HUMAN (WAT2018) is the result of the Pairwise Crowdsourcing Evaluation on WAT2018.
HUMAN (WAT2018) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2017)

Notice:

HUMAN (WAT2017) is the result of the Pairwise Crowdsourcing Evaluation on WAT2017.
HUMAN (WAT2017) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2016)

Notice:

HUMAN (WAT2016) is the result of the Pairwise Crowdsourcing Evaluation on WAT2016.
HUMAN (WAT2016) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.

HUMAN (WAT2015)

Notice:

HUMAN (WAT2015) is the result of the Pairwise Crowdsourcing Evaluation on WAT2015.
HUMAN (WAT2015) was evaluated by 5 different workers and the final decision is made by the voting of the judgements.
The detail of the evaluation can be found in the pdf document (PDF file).

HUMAN (WAT2014)

Notice:

HUMAN (WAT2014) is the result of the Pairwise Crowdsourcing Evaluation on WAT2014.
HUMAN (WAT2014) was evaluated by 3 different workers and the final decision is made by the voting of the judgements.
The detail of the evaluation can be found in the pdf document (PDF file).

EVALUATION RESULTS USAGE POLICY

When you use the WAT evaluation results for any purpose such as:
- writing technical papers,
- making presentations about your system,
- advertising your MT system to the customers,
you can use the information about translation directions, scores (including both automatic and human evaluations) and ranks of your system among others. You can also use the scores of the other systems, but you MUST anonymize the other system's names. In addition, you can show the links (URLs) to the WAT evaluation result pages.

NICT (National Institute of Information and Communications Technology)
Kyoto University
Last Modified: 2018-08-02

WAT The Workshop on Asian Translation Evaluation Results

BLEU

RIBES

AMFM

HUMAN (WAT2022)

HUMAN (WAT2021)

HUMAN (WAT2020)

HUMAN (WAT2019)

HUMAN (WAT2018)

HUMAN (WAT2017)

HUMAN (WAT2016)

HUMAN (WAT2015)

HUMAN (WAT2014)

EVALUATION RESULTS USAGE POLICY

WAT

The Workshop on Asian Translation

Evaluation Results