Smarter Soft Prompts

A single soft prompt for every input and every layer can be too blunt. These methods make soft prompts smarter and more selective.

Intuition

Different layers do different jobs. Different inputs need different hints. So we should not always:

How it works

SMoP — Sparse Mixture of Prompts

Plain-English idea: keep several prompt candidates, and activate only the useful ones for a given input (sparse mixture), instead of forcing one mega-prompt to do all the work.

APT — Adaptive Prefix Tuning

Plain-English idea: do not treat all layers equally. Change prefix length (prompt capacity) across layers.

Why that matters:

Task flavor Layer emphasis Why
Entity / relation extraction Bottom layers Local phrase structure matters a lot
Commonsense / causal reasoning Higher layers Semantic abstraction matters more

APT can also use gating so a layer only “keeps” the prefix tokens it needs.

IDPG — Instance-Dependent Prompt Generation

Plain-English idea: the right soft prompt should depend on this input, not only on the task name.

A small prompt-generator network builds prompt vectors from the input. Useful when one task has many subcases and a static prompt is too generic.

SPT — Selective Prompt Tuning

Plain-English idea: ask whether every layer needs soft prompting at all. Usually no. Learn to insert prompts only where they help.

What goes wrong

One-line summary

SMoP, APT, IDPG, and SPT make soft prompts selective — by mixture, by layer, by input instance, or by choosing where prompts are even needed.

Key terms