We thank the reviewer for their insightful comments and for appreciating the applicability and other strengths of our work.
*> The evaluation of human annotations focuses only on precision and does not investigate recall. However, the authors are open about this limitation.*
In order to measure recall, we would require ground truth annotations with all possible coherence errors in the summaries. However, prior studies (SNaC and Scarecrow) have discussed that this is challenging for subjective fine-grained evaluation tasks where annotators generally display high precision but low recall.
One solution could be to collect annotations from multiple annotations per summary, and consider their union as the exhaustive set of errors. Scarecrow and SNaC employ 10 and 3 annotators per summary respectively, but such a scheme would be very costly for our setting, as annotating 100 summaries already costs $1.5K. Annotation precision is more economical to evaluate, while also serving as an informative metric. We have updated Section 3 to make it clearer. We believe future work in human evaluation that makes recall-centric annotation more tractable is a promising area that could complement the precision-centric measurement we propose here.
*> Some of the examples of types of errors shown in Table 1 seem to be of questionable quality…*
This is a valid concern, and we appreciate the reviewer for pointing it out. We acknowledge that sometimes annotators or GPT-4 may ask questions that are also unanswered in the book, and there is no way to confirm without reading the source text. Using the reviewer’s example, if the identity of the mysterious man is not revealed in the book, the summary could say something like “A mysterious man whose identity is never revealed.” Since our focus is on coherence, the nature of our evaluation protocol is to have readers naturally raise questions as they read through a summary. Checking whether a question can be answered by the source text and finding answers to these questions would fall under faithfulness evaluation, which we leave to future work.
*> This may be a side effect of offering a monetary reward based in part on the number of annotations (cf. Appendix G).*
We appreciate the reviewer for going through the appendix. For the first evaluation task where we collected span-question pairs, we actually paid $15 USD per summary regardless of how many annotations were provided as mentioned in Section 3.
Appendix G (now J) is for the second human evaluation where we validated annotations collected from the first one. For this evaluation, we paid based on how many annotations from the first task an annotator had to annotate, which also did not incentivize them in any way. The annotators were informed of the second evaluation task a few weeks after they completed the first one, so payment for the second task could not have biased annotators to create more annotations for the first. We understand that this may be unclear, and have made clarifications in Appendix J.
*> The sentence-level score may disproportionately favor summaries that contain a large number of (short) sentences.*
We understand this concern. In practice, we do not observe significant differences in sentence length. We computed the average number of tokens per sentence for the 100 summaries collected under each configuration (10 in total). The minimum is 21, maximum is 28.3, and standard deviation is 2.5. Future work may decompose the summary into atomic units (like FactScore) before running fine-grained evaluation. However, this decomposition may be hard to automate.
*> Furthermore, the evaluation of different models does not further investigate whether some of the score differences can be explained by the different length of the summaries.*
This is a valid concern. We have added a plot of BOOOOKSCORE vs. summary length in Appendix F, which shows no correlation between the two.
*> Table 2: Why is there no entry for LLaMA2 in the incremental update section?*
This is explained in Section 5, we could not get LLaMA 2 to perform incremental updating.
*> Doesn't the choice of p = 1 for nucleus sampling disable it completely?*
You are correct, we have rephrased it in the paper.
*> The choice of a large temperature also seems rather unusual…have you investigated how stable the results are when the temperature is varied?*
We found that setting temperature to 0 affected generation quality in our preliminary experiments. Plus, prior to the recent OpenAI update, setting temperature to 0 for these closed-source models did not guarantee deterministic output. We did not study the effect of temperature on BOOOOKSCORE due to budget constraints.
*> shouldn't "lower" be "higher"?*
That is correct, we have changed it in the paper.
*> “Highly extractive" seems to contradict the large proportion of novel trigrams…*
“Highly extractive” is relative to other models. We have updated the paper with clarification.