Papers › Learning to Perturb Word Embeddings for Out-of-distribution QA

Learning to Perturb Word Embeddings for Out-of-distribution QA

6 May 2021ACL 2021 5arXiv:2105.02692archive 2025-07-28

Seanie Lee, Minki Kang, Juho Lee, Sung Ju Hwang

QA models based on pretrained language mod-els have achieved remarkable performance on various benchmark datasets.However, QA models do not generalize well to unseen data that falls outside the training distribution, due to distributional shifts.Data augmentation (DA) techniques which drop/replace words have shown to be effective in regularizing the model from overfitting to the training data.Yet, they may adversely affect the QA tasks since they incur semantic changes that may lead to wrong answers for the QA task. To tackle this problem, we propose a simple yet effective DA method based on a stochastic noise generator, which learns to perturb the word embedding of the input questions and context without changing their semantics. We validate the performance of the QA models trained with our word embedding perturbation on a single source dataset, on five different target domains.The results show that our method significantly outperforms the baselineDA methods. Notably, the model trained with ours outperforms the model trained with more than 240K artificially generated QA pairs.

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

By repository: official repository: 10 samples from 1 repository, 8 ran (4 with no instrument failure; 4 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.

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. 2 of the 8 samples that ran have no recorded date.

seanie12/SWEP officialmentioned on GitHubpytorchMITSyntology: 10 samples, 8 ran (4 instrument-failed) · 2 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

10 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 4 with no instrument failure: 2 honoured, 1 violated, 1 with no contract checked; 4 where Syntology's instrument failed) · 2 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.

2ran · honoured contract
1ran · violated contract
4ran · our draft was wrong
1ran
2unverified

Licence: 6 of the 10 samples are pointer only, meaning Syntology does not serve that copy's text. For 6 of them, this paper's copy is under a permissive licence and cleared, but the stored copy of the same code that Syntology serves is not; the licence label's tooltip gives Syntology's recorded reason. This page shows no code text for any sample; each one links to its file in the repository.

Harvested from seanie12/SWEP. “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.

seanie12/SWEP official repository 10 samples, 8 ran (4 instrument-failed) · 2 unverified
to_list in 62 papers run_squad.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 9df40357afea56cc · report fixture: signature tensor:Tensor/2/float · returned list · level recorded, date not recorded
compute_exact in 17 papers squad_metrics.py ran · honoured contract fingerprinted MIT (permissive) · 9026d9da5d085bd4 · report fixture: signature a_gold:str/0/str, a_pred:str/0/str · returned int · level recorded 2026-09-22
exact_match_score in 82 papers mrqa_utils.py ran · violated contract fingerprinted MIT (permissive) here; the stored copy is pointer only · bf75673211903e14 · report fixture: signature prediction:str/0/str, ground_truth:str/0/str · returned bool · level recorded 2026-09-22
f1_score in 121 papers mrqa_utils.py ran · honoured contract fingerprinted MIT (permissive) here; the stored copy is pointer only · cdf4b8c0fec3da02 · report fixture: signature prediction:str/0/str, ground_truth:str/0/str · returned float · level recorded 2026-09-22
get_dataloader in 111 papers run_squad.py ran MIT (permissive) · f4543e8ffa04b4d5 · report fixture: signature args:Args/0/?, features:list/1/Feature, is_training:bool/0/bool · returned DataLoader · level recorded 2026-09-25
get_tokens in 40 papers squad_metrics.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · aa6bc32d9c17a2f1 · report fixture: signature s:str/0/str · returned list · level recorded 2026-09-22
normalize_answer in 304 papers mrqa_utils.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · e7e75981cb464788 · report fixture: signature s:str/0/str · returned str · level recorded, date not recorded
normalize_answer in 304 papers squad_metrics.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 6a96435eba311b08 · report fixture: signature s:str/0/str · returned str · level recorded 2026-09-22
convert_examples_to_features in 134 papers squad_utils.py unverified MIT (permissive) · 5fa242f804a151c9 · report
process_batch in 31 papers run_squad.py unverified MIT (permissive) · 3ed8b1210b9d20a6 · report

Tasks

Data AugmentationDomain GeneralizationQuestion Answering

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