Evaluated on LaMP; added clarification on multi-turn Q&A, ICL, hate classification; added lambda=0 for Table 2.
> Include evaluations on established benchmarks
We thank the reviewer for the suggestions. Upon careful review, we think that there are some gaps in applying CoS on recommender systems in [2]. We have followed the procedures in [1] and applied CoS on LaMP-7 for tweet paraphrasing (the other tasks exceed our current context length limit). Our results are included in Appendix C.5, where we use the training set to find a set of high-performing lambda values and evaluate them on the held-out set. Interestingly, we find that lambda=-0.2 and lambda=-0.5 achieve the overall best performance, outperforming the proposed prompt (equivalent to lambda=0) in LaMP. We believe that the proposed prompt is highly verbose, and using smaller lambdas (i.e. lambda=-0.5) reduces this redundancy, leading to better generation. We think that this shows CoS’s utility in controllably setting the influence of the context.
> How multi-turn Q&A and in-context learning are compared under different lambda values. How do these outcomes demonstrate the proposed method's advantages?
We have updated Figure 4 to highlight that the multi-turn Q&A and in-context learning are generated under 0,1,2 and 3 rounds of interactions (ICL using the demonstration from GPT-4). The lambda values for CoS are selected from held-out examples such that the outputs roughly match the demonstration from GPT-4. Note that while we only plot lambda=0, 1, 1.5, and 3, CoS can provide more fine-grained results by setting lambda values to lie in between these values.
Compared to ICL: we find that ICL fails to generate fine-grained personalizations.
Compared to multi-turn QA: multi-turn QA leads to higher computational cost after round = 2, and unlike CoS, multi-turn QA cannot interpolate between discrete rounds.
> For the hate identification experiments, the results are not presented in a clear manner. How to compute lambda using equations (4) and (5)?
We have updated the descriptions for classifying and quantifying implicit hate and added formula for how we computed the most likely context and inferred the most likely lambda. Concretely to infer lambda, we perform forward inference over a set of increasing lambda spanning from -1 to 3 (interval 0.1), and select the lambda with the highest forward probability given the context (hateful intent) and generation (tweet).
> The method's effectiveness seems dependent on the LLM’s existing ability.
We fully agree with the author that CoS merely serves as a steering technique and the main generation capability comes from the base language model. We do find that for relevant contexts, LLM is highly steerable and for irrelevant contexts (appendix C.2), the generation is not influenced. There are limitations such as CoS cannot steer base text model towards instruction following, which can be achieved by tuning based methods.
> Table 2 does not include results for lambda=0.
We have updated Table 2 to include generation for lambda = 0.
> Ensure that the generated results remain fluent, coherent, and meaningful.
To ensure coherence, as well as ensuring that the generation is diverse and not repetitive, we added an additional study in sec 4.1 and appendix C.4 where we measure coherence and diversity of generated texts following Li et al 2023. We find that CoS naturally leads to diverse and coherent generations and that the lambda value has a small influence on both metrics.