Papers › Metric-Based In-context Learning: A Case Study in Text Simplification
Metric-Based In-context Learning: A Case Study in Text Simplification
Subha Vadlamannati, Gözde Gül Şahin
In-context learning (ICL) for large language models has proven to be a powerful approach for many natural language processing tasks. However, determining the best method to select examples for ICL is nontrivial as the results can vary greatly depending on the quality, quantity, and order of examples used. In this paper, we conduct a case study on text simplification (TS) to investigate how to select the best and most robust examples for ICL. We propose Metric-Based in-context Learning (MBL) method that utilizes commonly used TS metrics such as SARI, compression ratio, and BERT-Precision for selection. Through an extensive set of experiments with various-sized GPT models on standard TS benchmarks such as TurkCorpus and ASSET, we show that examples selected by the top SARI scores perform the best on larger models such as GPT-175B, while the compression ratio generally performs better on smaller models such as GPT-13B and GPT-6.7B. Furthermore, we demonstrate that MBL is generally robust to example orderings and out-of-domain test sets, and outperforms strong baselines and state-of-the-art finetuned language models. Finally, we show that the behaviour of large GPT models can be implicitly controlled by the chosen metric. Our research provides a new framework for selecting examples in ICL, and demonstrates its effectiveness in text simplification tasks, breaking new ground for more accurate and efficient NLG systems.
Code
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
Not run by Syntology. Nothing on this page verifies that the listed code works.
Tasks
Results from the paper archive 2025-07-28
| Task | Dataset | Model | Metric | Value | Rank at snapshot | Leaderboard | Report |
|---|---|---|---|---|---|---|---|
| Text Simplification | ASSET | GPT-175B (15 SARI-selected examples, random ordering) | BLEU | 73.92 | #1 of 12 | Archive leaderboard | report |
| Text Simplification | ASSET | GPT-175B (15 SARI-selected examples, random ordering) | FKGL | 7.73 | #1 of 12 | Archive leaderboard | report |
| Text Simplification | ASSET | GPT-175B (15 SARI-selected examples, random ordering) | SARI (EASSE>=0.2.1) | 47.94 | #1 of 12 | Archive leaderboard | report |
| Text Simplification | TurkCorpus | GPT-175B (6 SARI-selected examples, high/low) | BLEU | 79.83 | #1 of 25 | Archive leaderboard | report |
| Text Simplification | TurkCorpus | GPT-175B (6 SARI-selected examples, high/low) | FKGL | 9.33 | #1 of 25 | Archive leaderboard | report |
| Text Simplification | TurkCorpus | GPT-175B (6 SARI-selected examples, high/low) | SARI (EASSE>=0.2.1) | 43.46 | #1 of 25 | 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.
Methods
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