We thank the reviewer for valuable suggestions and comments. We address your questions below in detail with additional experiments and in-depth analysis.
**Regarding practical utility of ProMoT.** Thanks for the comments. We agree with the reviewer’s insight that the most significant application of ProMoT would be in domains where high quality finetuning data is limited. In such scenarios, it is imperative to have methods that are 1) robust against severe forgetting due to finetuning data homogeneity, which will cause format specialization as we extensively demonstrated in this work.
2) can maximize the value of each datapoint through improved generalization.
We would like to stress that this kind of situation is not a small niche, especially when language models are applied to new and complex domains where it is extremely difficult to collect high quality supervised finetuning data even for one task - autonomous LLM agents is one such area amongst many. Given this successful proof of concept, we believe that our method will open up new possibilities in these domains and will be of interest to a broad community of ICLR researchers.
**Regarding massive multi-task experiments.** Thanks for the comments. As discussed above, the focus of this work is more towards low data / high generalization requirement regime. With our best effort given computational resources constraints, we choose not to run massive multi-task training on large-scale datasets (such as the FLAN mixture, among others). However, as demonstrated by a recent work (Table 1 in https://openreview.net/pdf?id=VrHiF2hsrm), forgetting of in-context learning capabilities also exists in the massive multi-task regime, where methods like ProMoT could be helpful. We hope to explore the massive multi-task regime with ProMoT as a future work, but we do believe that our current results are self-contained, thorough and significant enough to be known by the community.
**Regarding 4-shot evaluation results.** Thanks for the suggestions. We have added the 4-shot evaluation results for fine-tuning v.s. ProMoT with multi-task training in the table below. As we can see from the table, the results are consistent with the 1-shot result that ProMoT can produce a generally better model on these evaluation tasks with 4-shots prompts. Note that as True/False format has been seen during fine-tuning, the model with standard fine-tuning can also do well on CB and WiC tasks. We have added this additional result to the Appendix.
| | Pretrained Model - 4-shots | Multi-task Finetune - 4-shots | Multi-task ProMoT - 4-shots |
|---------------|----------------------------|-------------------------------|-----------------------------|
| cb | 51.79 | 82.14 | 78.57 |
| wic | 49.69 | 52.82 | 52.5 |
| TriviaQA | 19.02 | 17.75 | 22.26 |
| Web_questions | 13.04 | 12.25 | 12.5 |
| WMT16 En-De | 8.83 | 0.24 | 18.84 |
| WMT16 En-Ro | 3.92 | 0.54 | 18.81 |
| XSum | 2.35 | 0.34 | 5.04 |
| WikiLingua/en | 1.33 | 0.39 | 1.92 |
**Regarding the Prefix + Parameter tuning baseline.** Thanks for the comments. We have included a ‘joint fine-tuning’ setting in the ablation study (Table 6), which trains the soft prompt and the main model jointly exactly as the comments suggested. In evaluation, we only use the main model and remove the soft prompt on evaluation tasks with different formats. As we can see from the table, the prefix + parameter tuning joint training still suffers from significant loss of general in-context learning performance, as the format learning can not be separated into the prompt if we train the two parts jointly.
**Regarding the prefix-tuning column.** Thank you for your suggestion on the table organization. For the source tasks, we report the in-domain performance of prompt-tuning in Table 2, showing that prompt-tuning is indeed inferior compared to standard finetuning or ProMoT in-domain. For evaluation on other tasks, exactly as the reviewer mentioned, since prompt tuning does not touch the parameters of the pretrained model, it has the same few-shot performance on evaluation tasks as the pretrain model where we remove the soft prompt. We have also made this clear to the audience in the footnotes of Table 3 and 4. We hope these would clarify the prompt tuning results well.