Papers › ELI5: Long Form Question Answering

ELI5: Long Form Question Answering

22 Jul 2019ACL 2019 7arXiv:1907.09190archive 2025-07-28

Angela Fan, Yacine Jernite, Ethan Perez, David Grangier, Jason Weston, Michael Auli

We introduce the first large-scale corpus for long-form question answering, a task requiring elaborate and in-depth answers to open-ended questions. The dataset comprises 270K threads from the Reddit forum ``Explain Like I'm Five'' (ELI5) where an online community provides answers to questions which are comprehensible by five year olds. Compared to existing datasets, ELI5 comprises diverse questions requiring multi-sentence answers. We provide a large set of web documents to help answer the question. Automatic and human evaluations show that an abstractive model trained with a multi-task objective outperforms conventional Seq2Seq, language modeling, as well as a strong extractive baseline. However, our best model is still far from human performance since raters prefer gold responses in over 86% of cases, leaving ample opportunity for future improvement.

PaperPDFConference PDFCodeCode 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 11 code samples harvested from 2 repositories linked to this paper: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 1 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 3 where our contract draft was wrong; failures of Syntology's instrument, not of the code.

By repository: official repository: 4 samples from 1 repository, 4 ran (1 with no instrument failure; 3 where Syntology's instrument failed); community (archive-listed): 7 samples from 1 repository, 6 ran (6 with no instrument failure; 0 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.

No sample is linked to this paper from 1 of its repositories that Syntology harvested for other papers:

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

facebookresearch/ELI5 officialmentioned in papermentioned on GitHubpytorchSyntology: 4 samples, 4 ran (3 instrument-failed) · 0 unverified report
ivabojic/sleepqa mentioned on GitHubpytorchMITSyntology: 7 samples, 6 ran (0 instrument-failed) · 1 unverified report
martiansideofthemoon/relic-retrieval mentioned on GitHubpytorchSyntology: no sample linked to this paper (harvested for another paper). Syntology's graph links these samples to REALM: Retrieval-Augmented Language Model Pre-Training (arXiv:2002.08909; that paper's own run record: 4 ran (of which 1 constructed an object rather than computing a result; 3 with no instrument failure: 0 honoured, 2 violated, 1 with no contract checked; 1 where Syntology's instrument failed) · 0 unverified); nothing checks that they implement this paper's method. 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.

A paper named beside a repository with no sample linked to this paper is shown with that paper's own run record, not this paper's: “ran” means executed on a synthesized input, not that the code is correct, and “where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Papers are listed in arXiv-id order, at most three per repository.

Code Syntology ran Syntology

11 samples harvested: 10 ran (of which 0 constructed an object rather than computing a result; 7 with no instrument failure: 0 honoured, 1 violated, 6 with no contract checked; 3 where Syntology's instrument failed) · 1 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 · violated contract
3ran · our draft was wrong
6ran
1unverified

Licence: 4 of the 11 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 2 repositories linked to this paper, official or community; the list below is grouped by repository, each group headed by its name and what it is to the paper. “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.

A function or class name links to its page when the name occurs in the harvested code of at least 5 papers; the name is a string, not an identity.

facebookresearch/ELI5 official repository 4 samples, 4 ran (3 instrument-failed) · 0 unverified
form_multitask model_code/process_data_to_source_target.py ran · our draft was wrong licence not identified · pointer only · 85249de6d23a4c95 · report fixture: signature questions:list/1/str, documents:list/1/str, answers:list/1/str · returned tuple · level recorded 2026-09-22
form_multitask_valid model_code/process_data_to_source_target.py ran · our draft was wrong licence not identified · pointer only · c9f24e3c7f4f3a6d · report fixture: signature questions:list/1/str, documents:list/1/str, answers:list/1/str · returned tuple · level recorded 2026-09-22
read_data in 132 papers model_code/process_data_to_source_target.py ran · our draft was wrong licence not identified · pointer only · b6d13c7a498e6427 · report fixture: signature json_input:str/0/str · returned tuple · level recorded 2026-09-22
valid_comment data_creation/download_reddit_qalist.py ran · violated contract licence not identified · pointer only · 9c5f8497fc6fad52 · report fixture: signature a:dict/0/? · returned bool · level recorded 2026-09-22
ivabojic/sleepqa community (archive-listed) 7 samples, 6 ran (0 instrument-failed) · 1 unverified
convert in 76 papers eval/human_eval.py ran fingerprinted MIT (permissive) · b48cb9361ebbb228 · report fixture: signature int_number:int/0/int · returned ndarray · level recorded 2026-09-24
get_ac1 eval/human_eval.py ran fingerprinted MIT (permissive) · a8e5fab653d001cb · report fixture: signature preds_mat:ndarray/2/float · returned float64 · level recorded 2026-09-24
prep in 5 papers utils/f1_score.py ran fingerprinted MIT (permissive) · 70884b9d73bb5d1f · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-24
read_file in 112 papers eval/auto_eval.py ran MIT (permissive) · b127fbfb02fb0632 · report fixture: signature file_name:str/0/str · returned list · level recorded 2026-09-24
tokenize in 176 papers utils/f1_score.py ran MIT (permissive) · 30cc0698334579ce · report fixture: signature sentences:list/1/str · returned list · level recorded 2026-09-24
word_extraction utils/f1_score.py ran fingerprinted MIT (permissive) · bc849309561f999d · report fixture: signature sentence:str/0/str · returned list · level recorded 2026-09-24
load_states_from_checkpoint models/convert_dpr_original_checkpoint_to_pytorch.py unverified MIT (permissive) · f4d8181b299c2aa9 · report

Tasks

FormLanguage ModelingLanguage ModellingLong Form Question AnsweringOpen-Domain Question AnsweringQuestion AnsweringSentence

Datasets

Introduced by this paper, per the archive.

ELI5

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

Methods

LSTMSeq2SeqSigmoid ActivationTanh Activation

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