Papers › Reordering Examples Helps during Priming-based Few-Shot Learning
Reordering Examples Helps during Priming-based Few-Shot Learning
Sawan Kumar, Partha Talukdar
The ability to learn from limited data, or few-shot learning, is a desirable and often critical requirement for NLP systems. While many existing methods do poorly at learning from a handful of examples, large pretrained language models have recently been shown to be efficient few-shot learners. One approach to few-shot learning, which does not require finetuning of model parameters, is to augment the language model's input with priming text which is typically constructed using task specific descriptions and examples. In this work, we further explore priming-based few-shot learning, with focus on using examples as prompts. We show that presenting examples in the right order is key for generalization. We introduce PERO (Prompting with Examples in the Right Order), where we formulate few-shot learning as search over the set of permutations of the training examples. We show that PERO can learn to generalize efficiently using as few as 10 examples, in contrast to existing approaches. While the newline token is a natural choice for separating the examples in the prompt, we show that learning a new separator token can potentially provide further gains in performance. We demonstrate the effectiveness of the proposed method on the tasks of sentiment classification, natural language inference and fact retrieval. Finally, we analyze the learned prompts to reveal novel insights, including the idea that two training examples in the right order alone can provide competitive performance for sentiment classification and natural language inference.
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):
get_harvested_code_for_paper(arxiv_id="2106.01751")get_code(code_sha256="…")with a sample'scode_sha256from the list belowget_citation_path(paper_1="2106.01751", paper_2="…")with another paper's arXiv id or titleget_concepts_for_paper(arxiv_id="2106.01751")
Code
Syntology 7 code samples harvested from 2 repositories linked to this paper: 3 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 4 unverified. Where Syntology's instrument failed: 1 where our contract draft was wrong; failures of Syntology's instrument, not of the code.
By repository: official repository: 3 samples from 1 repository, 0 ran (0 with no instrument failure; 0 where Syntology's instrument failed); found in paper text by Syntology: 4 samples from 1 repository, 3 ran (2 with no instrument failure; 1 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 on 2026-09-22 (UTC): the dates Syntology's graph wrote each sample's verification level, not when the code executed.
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
7 samples harvested: 3 ran (of which 2 constructed an object rather than computing a result; 2 with no instrument failure: 0 honoured, 0 violated, 2 with no contract checked; 1 where Syntology's instrument failed) · 4 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.
Licence: 0 of the 7 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.
bfaef19b1a497d58 · report
fixture: returned PredictWrapper · level recorded 2026-09-22 cb904be0b5c6abc4 · report
fixture: returned TriggerTemplatizer · level recorded 2026-09-22 c8fc624ca613854e · report
fixture: signature fname:PosixPath/0/?, templatizer:callable/0/?, use_ctx:bool/0/bool, limit:int/0/int · returned list · level recorded 2026-09-22 de4d142f8cd18f36 · report
Method as code Syntology
What Syntology's graph records as this paper's claimed method, lifted into code: each assembly names its bricks (functions and classes), each with its own role and its own verification level. An assembly is not a check that the code implements the method correctly or reproduces the paper's results. Levels are each brick's own verification level in Syntology's graph (level 0: no recorded run), listed brick by brick and never combined into one level; “ran” means the brick executed on a synthesized input, not that its output is correct, and the instrument figure counts failures of Syntology's instrument, not of the code. Where a model read the code against the paper's claim, each assembly's label verdict is one model's judgement, kept in this page's JSON twin; it is not calibrated, so no card prints it. Siblings are assemblies lifted from this paper in the same batch for the same method: alternative readings kept side by side; none replaces or supersedes another.
2 assemblies on this paper: 2 harvested, 0 generated, listed in 1 groups (siblings lifted in one batch form one group).
2 sibling assemblies for PERO (harvested), lifted in the same batch on 2026-09-09: alternative readings kept side by side; none replaces or supersedes another.
harvested Assembly for PERO (graph method: PERO). 20 bricks; individually on a fixture: 16 ran (of which 5 constructed an object rather than computing a result; 8 with no instrument failure: 2 honoured, 1 violated, 5 with no contract checked; 8 where Syntology's instrument failed) · 4 unverified. The assembly has not been run end-to-end.
one of 2 siblings
- run_model entry · level 0 · unverified ·
de4d142f8cd18f36 - AccuracyFn metric · level 1 · ran ·
03ba856c8d50cb92 - Collator helper · level 1 · ran ·
736b1e3d7a04f0c0 - GradientStorage helper · level 1 · ran ·
3109240945514efb - PredictWrapper model · level 1 · ran ·
bfaef19b1a497d58 - TriggerTemplatizer helper · level 1 · ran ·
cb904be0b5c6abc4 - encode_label helper · level 1 · ran · honoured contract ·
d174dc1e0823ae67 - get_embeddings helper · level 1 · ran · our draft was wrong ·
20a9293a820f617d - get_loss loss · level 1 · ran; the contract check could not run ·
f614f524884546fe - hotflip_attack update_rule · level 1 · ran; the contract check could not run ·
309e71f4157403d6 - isupper helper · level 1 · ran · violated contract ·
6a57ad8e1ebd28ac - load_augmented_trigger_dataset helper · level 1 · ran · our draft was wrong ·
167ee534ecb844a1 - load_pretrained helper · level 0 · unverified ·
a5946a0ceaabfe6b - load_trigger_dataset helper · level 1 · ran · our draft was wrong ·
c8fc624ca613854e - set_seed helper · level 0 · unverified ·
52e446206cdc2fa5 - pad_squeeze_sequence helper · level 1 · ran · honoured contract ·
d133860668e93507 - replace_trigger_tokens data_transform · level 1 · ran; the contract check could not run ·
ec5d1f66dd9187f9 - add_task_specific_tokens helper · level 0 · unverified ·
02ee33f23a8f0591 - load_jsonl helper · level 1 · ran · our draft was wrong ·
3193029e7175ef98 - load_tsv helper · level 1 · ran · our draft was wrong ·
e284d68f65c1afe4
harvested Assembly for PERO (graph method: PERO). 3 bricks; individually on a fixture: 0 ran · 3 unverified. The assembly has not been run end-to-end.
one of 2 siblings
- GA entry · level 0 · unverified ·
fa053ba6d77847c8 - PermutationHandler helper · level 0 · unverified ·
ce83164ae06e5fae - SInstance helper · level 0 · unverified ·
8bda67b843418308
Each brick ends with its code_sha256, Syntology's identity for that exact code; click one to copy the get_code call that returns it. For agents, on Syntology's MCP service: assembly(arxiv_id="2106.01751") returns these assemblies with each brick's role and wiring (how to connect).
Tasks
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