Browse State-of-the-Art › Lay Summarization

Lay Summarization

5 papers with code · 2 benchmarks · 4 datasets archive 2025-07-28

Natural Language Processing

Summarizing a technical or scientific document in simple, non-technical language that is comprehensible to a lay person (non-expert).

Description from the archive archive 2025-07-28.

Benchmarks archive 2025-07-28

2 leaderboard tables shown for this task, 2 with rows (a “benchmark” on this site is a table with at least one row, as on /sota), ordered by row count. “Best model” is the first row in the archive's own order at snapshot; nothing is re-ranked here and metric direction is not recorded in the archive. PwC's Trend sparklines are not in the archive, so that column is omitted.

DatasetBest model (first row in archive order)PaperCodeSyntologyCompare
eLife (1 row) BART Making Science Simple: Corpora for the Lay Summarisation of... code — Compare
PLOS (1 row) BART Making Science Simple: Corpora for the Lay Summarisation of... code — Compare

Syntology column: samples harvested from the paper's repositories and executed on synthesized fixtures; “ran” is not a correctness claim and does not order the table. Each line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the instrument figure counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the row's paper, the line starts with that repository's state (“official” is the archive's flag, not a verdict on who wrote the code; “community repositories only” when every sample that ran came from a community repository, “official: no sample here; runs from other or unrecorded repositories” when some came from a repository the paper names or has in its text, or from none recorded); hover it for the repositories the samples that ran came from. A dash means no Syntology record for that paper, not a recorded non-run. Each “ran” line links to that paper's sample list. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. For agents: get_harvested_code_for_paper(arxiv_id) lists each paper's samples; how to connect.

Libraries

Not in the archive: the export carries no per-task library table, so there is nothing to show at snapshot 2025-07-28.

Datasets archive 2025-07-28

4 datasets whose archive record lists this task, ordered by the archive's paper count.

Subtasks archive 2025-07-28

No subtask under this task in the archive's task tree.

Parent tasks archive 2025-07-28

Papers archive 2025-07-28

archive papers tagged: 11 · with a code link: 5 · where Syntology ran a sample: 0 (0 with a run with no instrument failure, 0 where every run was a failure of Syntology's instrument) Syntology

Show: all tagged papersonly where code ran: none of the 11 tagged papers has a Syntology run on record

Page 1 of 1: papers 1 to 11 of 11, in archive order: by repositories listed in the archive (most first), then newest first, not by stars (the archive holds no stars, so PwC's “Social” and “Latest” sorts cannot be reproduced). Papers that list no repository come after every paper that lists one.

Papers without a page here are shown as plain text. A Syntology line reads “N ran (of which C constructed an object rather than computing a result; K with no instrument failure: H honoured, V violated, P with no contract checked; I where Syntology's instrument failed) · U unverified”; the figure “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. When the archive marks a repository official for the paper, the line starts with that repository's state (the archive's flag, not a verdict on who wrote the code); hover it for the repositories the samples that ran came from.

  • 16 Oct 2023 1 repository listed
    Readability refers to how easily a reader can understand a written text.
  • 18 Oct 2022 1 repository listed
    Lay summarisation aims to jointly summarise and simplify a given text, thus making its content more comprehensible to non-experts.
  • 1 Nov 2020 1 repository listed
    Lay summarization aims to generate lay summaries of scientific papers automatically.
  • 1 Nov 2020 1 repository listed
    We describe our approach for the 1st Computational Linguistics Lay Summary Shared Task CL-LaySumm20.
  • 19 Oct 2020 1 repository listed
    Lay summarization aims to generate lay summaries of scientific papers automatically.
  • Explanatory Summarization with Discourse-Driven Planning
    27 Apr 2025 0 repositories listed
    Lay summaries for scientific documents typically include explanations to help readers grasp sophisticated concepts or arguments.
  • 16 Aug 2024 0 repositories listed
    Lay summarization is essential but challenging, as it simplifies scientific information for non-experts and keeps them updated with the latest scientific knowledge.
  • Overview of the BioLaySumm 2024 Shared Task on the Lay Summarization of Biomedical Research Articles
    16 Aug 2024 0 repositories listed
    This paper presents the setup and results of the second edition of the BioLaySumm shared task on the Lay Summarisation of Biomedical Research Articles, hosted at the BioNLP Workshop at ACL 2024.
  • WisPerMed at BioLaySumm: Adapting Autoregressive Large Language Models for Lay Summarization of Scientific Articles
    20 May 2024 0 repositories listed
    This paper details the efforts of the WisPerMed team in the BioLaySumm2024 Shared Task on automatic lay summarization in the biomedical domain, aimed at making scientific publications accessible to non-specialists.
  • Overview of the BioLaySumm 2023 Shared Task on Lay Summarization of Biomedical Research Articles
    29 Sep 2023 0 repositories listed
    This paper presents the results of the shared task on Lay Summarisation of Biomedical Research Articles (BioLaySumm), hosted at the BioNLP Workshop at ACL 2023.
  • Using Pre-Trained Transformer for Better Lay Summarization
    1 Nov 2020 0 repositories listed
    In this paper, we tack lay summarization tasks, which aim to automatically produce lay summaries for scientific papers, to participate in the first CL-LaySumm 2020 in SDP workshop at EMNLP 2020.

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