polish-nlp-eval
Evaluation of Transfer Learning for Polish with a Text-to-Text Model — Chrabrowa et al. (2022) (arXiv:2205.08808, 2022)
What this evaluates
Evaluates Polish language understanding, summarization, and question answering capabilities of text-to-text models. It probes how well encoder-decoder and decoder-only architectures generalize from multilingual pre-training to monolingual Polish tasks using exact-match generation and ROUGE-based metrics.
Datasets
- KLEJ benchmark — total ?; splits: train (-1), val (-1), test (-1)
- Allegro Articles — total 33000; splits: train (-1), test (-1)
- Polish Summaries Corpus — total 569; splits: train (-1), test (-1)
Metrics
exact-match accuracy (primary) — range: [0, 1]
- Percentage of test instances where the generated token sequence exactly matches the gold label. For specific KLEJ tasks, F1, Spearman correlation, or MAE-based scores are used instead.
ROUGE AVG — range: [0, 1]
- Arithmetic mean of the F-measure scores for ROUGE-1, ROUGE-2, and ROUGE-L. Calculated as (ROUGE-1 + ROUGE-2 + ROUGE-L) / 3.
Input / output format
Input: Text-to-text prompts with descriptive prefixes (e.g., '<Prefix 1>: text 1 <Prefix 2>: text 2' for KLEJ), trimmed source texts (typically ≤1024 tokens for summarization), and question-context pairs for QA.
Output: Greedy token generation until EOS or max target length. For KLEJ, semantically significant text tokens matching the gold label. For summarization/QA, generated text sequences.
Scoring recipe
def score(predictions, golds, task_type):
if task_type == 'classification':
return sum(1 for p, g in zip(predictions, golds) if p == g) / len(golds)
elif task_type == 'summarization':
r1 = rouge_fmeasure(predictions, golds, n=1)
r2 = rouge_fmeasure(predictions, golds, n=2)
rl = rouge_fmeasure(predictions, golds, n='l')
return (r1 + r2 + rl) / 3
Common pitfalls
- Input truncation to ~1024 tokens severely limits context for summarization, meaning models never see 100% of source text during training.
- Exact-match scoring is strict; only precise token matches count as correct, ignoring semantic equivalence.
- ROUGE metrics are noted as imperfect for abstractive summaries, with human upper bounds sometimes matching model performance.
Evidence (verbatim from paper)
Targets were generated over the whole vocabulary, and only an exact match was treated as the correct answer. Results are shown in Table 4 which contains arithmetic mean of (f-measure) ROUGE-1, ROUGE-2 and ROUGE-L (Lin, 2004) for each model and task.
Citation
@misc{chrabrowa2022evaluation,
title={Evaluation of Transfer Learning for Polish with a Text-to-Text Model},
author={Chrabrowa et al. (2022)},
year={2022},
note={arXiv:2205.08808}
}
1---2name: polish-nlp-eval3description: Evaluates Polish language understanding, summarization, and question answering capabilities of text-to-text models. It probes how well encoder-decoder and decoder-only architectures generalize from multilingual pre-training to monolingual Polish tasks using exact-match generation and ROUGE-based metrics. Use when the user wants to benchmark on KLEJ benchmark, Allegro Articles, Polish Summaries Corpus, or asks about evaluating this task. Reports exact-match accuracy.4---56# polish-nlp-eval78> Evaluation of Transfer Learning for Polish with a Text-to-Text Model — Chrabrowa et al. (2022) (arXiv:2205.08808, 2022)910## What this evaluates1112Evaluates Polish language understanding, summarization, and question answering capabilities of text-to-text models. It probes how well encoder-decoder and decoder-only architectures generalize from multilingual pre-training to monolingual Polish tasks using exact-match generation and ROUGE-based metrics.1314## Datasets1516- **KLEJ benchmark** — total ?; splits: train (-1), val (-1), test (-1)17- **Allegro Articles** — total 33000; splits: train (-1), test (-1)18- **Polish Summaries Corpus** — total 569; splits: train (-1), test (-1)1920## Metrics2122- `exact-match accuracy` **(primary)** — range: [0, 1]23 - Percentage of test instances where the generated token sequence exactly matches the gold label. For specific KLEJ tasks, F1, Spearman correlation, or MAE-based scores are used instead.24- `ROUGE AVG` — range: [0, 1]25 - Arithmetic mean of the F-measure scores for ROUGE-1, ROUGE-2, and ROUGE-L. Calculated as (ROUGE-1 + ROUGE-2 + ROUGE-L) / 3.2627## Input / output format2829**Input**: Text-to-text prompts with descriptive prefixes (e.g., '<Prefix 1>: text 1 <Prefix 2>: text 2' for KLEJ), trimmed source texts (typically ≤1024 tokens for summarization), and question-context pairs for QA.3031**Output**: Greedy token generation until EOS or max target length. For KLEJ, semantically significant text tokens matching the gold label. For summarization/QA, generated text sequences.3233## Scoring recipe3435```python36def score(predictions, golds, task_type):37 if task_type == 'classification':38 return sum(1 for p, g in zip(predictions, golds) if p == g) / len(golds)39 elif task_type == 'summarization':40 r1 = rouge_fmeasure(predictions, golds, n=1)41 r2 = rouge_fmeasure(predictions, golds, n=2)42 rl = rouge_fmeasure(predictions, golds, n='l')43 return (r1 + r2 + rl) / 344```4546## Common pitfalls4748- Input truncation to ~1024 tokens severely limits context for summarization, meaning models never see 100% of source text during training.49- Exact-match scoring is strict; only precise token matches count as correct, ignoring semantic equivalence.50- ROUGE metrics are noted as imperfect for abstractive summaries, with human upper bounds sometimes matching model performance.5152## Evidence (verbatim from paper)5354> Targets were generated over the whole vocabulary, and only an exact match was treated as the correct answer. Results are shown in Table 4 which contains arithmetic mean of (f-measure) ROUGE-1, ROUGE-2 and ROUGE-L (Lin, 2004) for each model and task.5556## Citation5758```bibtex59@misc{chrabrowa2022evaluation,60 title={Evaluation of Transfer Learning for Polish with a Text-to-Text Model},61 author={Chrabrowa et al. (2022)},62 year={2022},63 note={arXiv:2205.08808}64}65```6667- arXiv: 2205.08808