Papers › Do prompt positions really matter?

Do prompt positions really matter?

23 May 2023arXiv:2305.14493archive 2025-07-28

Junyu Mao, Stuart E. Middleton, Mahesan Niranjan

Prompt-based models have gathered a lot of attention from researchers due to their remarkable advancements in the fields of zero-shot and few-shot learning. Developing an effective prompt template plays a critical role. However, prior studies have mainly focused on prompt vocabulary searching or embedding initialization within a predefined template with the prompt position fixed. In this empirical study, we conduct the most comprehensive analysis to date of prompt position for diverse Natural Language Processing (NLP) tasks. Our findings quantify the substantial impact prompt position has on model performance. We observe that the prompt positions used in prior studies are often sub-optimal, and this observation is consistent even in widely used instruction-tuned models. These findings suggest prompt position optimisation as a valuable research direction to augment prompt engineering methodologies and prompt position-aware instruction tuning as a potential way to build more robust models in the future.

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

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

milliemaoo/prompt-position officialmentioned in paperMITSyntology: 11 samples, 8 ran (6 instrument-failed) · 3 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

11 samples harvested: 8 ran (of which 0 constructed an object rather than computing a result; 2 with no instrument failure: 1 honoured, 1 violated, 0 with no contract checked; 6 where Syntology's instrument failed) · 3 unverified. “Where Syntology's instrument failed” counts failures of Syntology's instrument, not of the code. Syntology's record for this page last changed ; when this build read Syntology's graph is in the build record. That date is not when the samples ran.

1ran · honoured contract
1ran · violated contract
6ran · our draft was wrong
3unverified

Licence: 7 of the 11 samples are pointer only, meaning Syntology does not serve that copy's text. For 7 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 milliemaoo/prompt-position. “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.

milliemaoo/prompt-position official repository 11 samples, 8 ran (6 instrument-failed) · 3 unverified
mean in 84 papers lm_eval/metrics.py ran · violated contract fingerprinted MIT (permissive) · 0928f497e20fb443 · report fixture: signature arr:list/1/float · returned float · level recorded, date not recorded
escaped_split in 10 papers lm_eval/utils.py ran · our draft was wrong MIT (permissive) · 57e732507bad40db · report fixture: signature text:str/0/str, sep_char:str/0/str, maxsplit:int/0/int · returned list · level recorded 2026-09-24
get_result in 30 papers lm_eval/models/gpt3.py ran · honoured contract MIT (permissive) here; the stored copy is pointer only · d253589f2c78dad0 · report fixture: signature response:dict/0/?, ctxlen:int/0/int · returned tuple · level recorded 2026-09-24
group in 18 papers lm_eval/utils.py ran · our draft was wrong MIT (permissive) here; the stored copy is pointer only · 359c35fdcd7a0ee5 · report fixture: signature arr:list/1/dict, fn:callable/0/? · returned list · level recorded 2026-09-24
hash_args in 46 papers lm_eval/base.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · ea06eaae4fc1eaf0 · report fixture: signature attr:str/0/str, args:tuple/1/int · returned str · level recorded 2026-09-22
pop_stddev in 10 papers lm_eval/metrics.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · 518b2201c66c2ad3 · report fixture: signature arr:list/1/float · returned float · level recorded 2026-09-24
sample_stddev in 11 papers lm_eval/metrics.py ran · our draft was wrong fingerprinted MIT (permissive) · d40f0123e8a8f5c0 · report fixture: signature arr:list/1/float · returned float · level recorded, date not recorded
simple_parse_args_string in 12 papers lm_eval/utils.py ran · our draft was wrong fingerprinted MIT (permissive) here; the stored copy is pointer only · cd999ad59caf84a7 · report fixture: signature args_string:str/0/str · returned dict · level recorded 2026-09-24
anthropic_completion lm_eval/models/anthropic_llms.py unverified MIT (permissive) · a5cf72836c37574e · report
make_table in 15 papers lm_eval/evaluator.py unverified MIT (permissive) here; the stored copy is pointer only · 9d95c14130837ee4 · report
stop_sequences_criteria in 5 papers lm_eval/models/huggingface.py unverified MIT (permissive) here; the stored copy is pointer only · 069ffbe9aadaa2ae · report

Tasks

Few-Shot LearningNatural Language UnderstandingPrompt Engineering

1 archive task tag without a task page not shown.

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