Papers › Asking Questions the Human Way: Scalable Question-Answer Generation from Text Corpus

Asking Questions the Human Way: Scalable Question-Answer Generation from Text Corpus

27 Jan 2020arXiv:2002.00748archive 2025-07-28

Bang Liu, Haojie Wei, Di Niu, Haolan Chen, Yancheng He

The ability to ask questions is important in both human and machine intelligence. Learning to ask questions helps knowledge acquisition, improves question-answering and machine reading comprehension tasks, and helps a chatbot to keep the conversation flowing with a human. Existing question generation models are ineffective at generating a large amount of high-quality question-answer pairs from unstructured text, since given an answer and an input passage, question generation is inherently a one-to-many mapping. In this paper, we propose Answer-Clue-Style-aware Question Generation (ACS-QG), which aims at automatically generating high-quality and diverse question-answer pairs from unlabeled text corpus at scale by imitating the way a human asks questions. Our system consists of: i) an information extractor, which samples from the text multiple types of assistive information to guide question generation; ii) neural question generators, which generate diverse and controllable questions, leveraging the extracted assistive information; and iii) a neural quality controller, which removes low-quality generated data based on text entailment. We compare our question generation models with existing approaches and resort to voluntary human evaluation to assess the quality of the generated question-answer pairs. The evaluation results suggest that our system dramatically outperforms state-of-the-art neural question generation models in terms of the generation quality, while being scalable in the meantime. With models trained on a relatively smaller amount of data, we can generate 2.8 million quality-assured question-answer pairs from a million sentences found in Wikipedia.

PaperPDFCodeCode 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 8 code samples: 7 from 2 repositories linked to this paper, 1 identical to code harvested from another paper's repository. Across all 8: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 where Syntology's instrument failed) · 1 unverified. Where Syntology's instrument failed: 1 where the contract check could not run; failures of Syntology's instrument, not of the code.

By repository: official repository: 6 samples from 1 repository, 6 ran (6 with no instrument failure; 0 where Syntology's instrument failed); community (archive-listed): 1 sample from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); 1 identical to code first harvested elsewhere. The run record, sample by sample. “Ran” means executed on a synthesized input, not that the code is correct or reproduces the paper.

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

bangliu/ACS-QG officialmentioned in paperpytorchMITSyntology: 6 samples, 6 ran (0 instrument-failed) · 0 unverified report
vijayakuruba/IFT6010_Applying_Answer-Clue-Style_Approach_to_VQG mentioned on GitHubpytorchSyntology: 1 sample, 0 ran · 1 unverified 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.

Code Syntology ran Syntology

8 samples harvested: 7 ran (of which 0 constructed an object rather than computing a result; 6 with no instrument failure: 0 honoured, 0 violated, 6 with no contract checked; 1 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; the contract check could not run
6ran
1unverified

Licence: 2 of the 8 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. 1 sample is listed last, in a group without a repository. “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. A census tag appears when Syntology's census ran implementations with that name on one shared input per bucket: it gives how many were compared, from how many papers, and how many distinct outputs they produced, and names this sample's bucket when this sample was one of them.

bangliu/ACS-QG official repository 6 samples, 6 ran (0 instrument-failed) · 0 unverified
NMTLoss loss/text_generation_losses.py ran MIT (permissive) · e497bfb3e5a79325 · report fixture: signature vocabSize:int/0/int · returned NLLLoss · level recorded 2026-09-25
QGLoss loss/text_generation_losses.py ran MIT (permissive) · 0c599636d7bd4df1 · report fixture: signature g_prob_t:Tensor/3/float, g_targets:Tensor/2/int, c_outputs:Tensor/3/float, c_switch:Tensor/2/float, c_gate_values:Tensor/3/float, c_targets:Tensor/2/int, crit:callable/0/?, copyCrit:callable/0/? · returned Tensor · level recorded 2026-09-25
SoftQGLoss1 loss/text_generation_losses.py ran MIT (permissive) · d2f6eae830c59871 · report fixture: signature g_prob_t:Tensor/3/float, g_targets:Tensor/2/int, c_outputs:Tensor/3/float, c_switch:Tensor/2/float, c_gate_values:Tensor/3/float, c_targets:Tensor/2/int, crit:callable/0/?, copyCrit:callable/0/?, soft_g_outputs:Tensor/3/float, new_g_outputs:Tensor/3/float · returned Tensor · level recorded 2026-09-25
get_perplexity in 8 papers DE_main.py ran fingerprinted MIT (permissive) · 064999a28f4d0b4b · report fixture: signature sentence:str/0/str · returned int · level recorded 2026-09-25
normalize_text in 60 papers DA_main.py ran fingerprinted MIT (permissive) · d53579a101181ef7 · report fixture: signature text:str/0/str · returned str · level recorded 2026-09-25
post_process in 56 papers QG_postprocess_seq2seq.py ran fingerprinted MIT (permissive) · 04dfc0720567cfda · report fixture: signature input:str/0/str · returned str · level recorded 2026-09-25
vijayakuruba/IFT6010_Applying_Answer-Clue-Style_Approach_to_VQG community (archive-listed) 1 sample, 0 ran · 1 unverified
sample_sequence in 8 papers GPT2_QG/interact.py unverified no licence file found · pointer only · 65e4d15139e1f262 · report
Repository not located 1 sample, 1 ran (1 instrument-failed) · 0 unverified
1 sample is identical to code Syntology harvested from another paper's repository; this paper's own copy was not located, so no repository is named and no licence is recorded.
top_filtering in 13 papers
census: 5 implementations from 9 papers, 1 distinct output on one shared input this sample: bucket 1 of 1, arg 1: rank 1, kind float, dtype float32
repository not located ran; the contract check could not run (RAISES) · metamorphic tier: invariant licence of this copy not recorded · 695eaa24be6f2a1d · report fixture: signature logits:Tensor/1/float, top_k:int/0/int, top_p:float/0/float, threshold:float/0/float, filter_value:float/0/float · returned Tensor · level recorded 2026-09-22

Tasks

Answer GenerationChatbotMachine Reading ComprehensionQuestion AnsweringQuestion GenerationQuestion-Answer-GenerationQuestion-GenerationReading Comprehension

Results from the paper archive 2025-07-28

No leaderboard rows for this paper in the archive.

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