- Rating
- 3(+2)
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 1
Read review
Paper summary
The authors test how accurately an LLM can summarize the important points, or cruxes, in its reasoning. A crux is defined as a reasoning step where changing the result of that step during the reasoning process would noticeably impact the final outcome. The authors are interested in two settings where extracting the crux is important. First, they test if a model can estimate the cruxes in its future reasoning \emph{a priori} (before producing the reasoning trace). This ability allows the LLM to summarize the information it needs to solve a task beforehand, and might be useful for delegating tasks to sub-agents. Second, they test an \emph{a posteriori} case (after producing the reasoning trace). An LLM which is good at this can summarize the key steps in its reasoning and is therefore easier to, e.g., build guardrails around.
In both cases, the predictions of the cruxes are generated by the same model which is used to solve the problem. The authors test if these predictions are indeed the key steps that are used by the model by comparing against a baseline “most accurate” method. This method works by first computing answers with reasoning for a task. Then, different pairs of reasoning traces are compared to one another to identify intermediate facts that both traces disagree on. These intermediate facts are stored as cruxes. Note that this method of identifying cruxes is inconsistent with the definition of crux from the previous paragraph, which I summarized from the author’s own definition in the abstract. This method simply finds facts that a model does not take a consistent stance on, it does not identify key reasoning steps which are likely to significantly change the downstream answer. The authors use Qwen3-Reranker-8B instead of a typical LLM judge to make the pairwise comparisons more computationally efficient.
The authors find that LLMs cannot accurately identify the cruxes of their argument. Overall, the three methods above predict cruxes that are inconsistent with one another.
Critical strengths
The problem is well-motivated. If a LLM can accurately identify the important parts of its upcoming reasoning, that ability can improve inference.
It is interesting that LLMs are not good at a priori predicting the important facts they will need to solve a problem. I feel there is interesting work to done by exploring this particular result further and with a more direct experiment.
The idea to identify cruxes by comparing multiple reasoning traces makes sense. Although the way the authors execute this comparison is inconsistent with the definition of a crux as an important reasoning step which can change the final answer.
Critical weaknesses
The authors do not find cruxes by checking which reasoning steps change the final answer across different rollouts. Instead, they are extracted by asking a LLM to identify which facts a pair of reasoning traces disagree on. There are many important reasoning steps where a LLM could take a consistent stance across rollouts, and the many-shot method would not identify these steps as cruxes.
The authors only directly queried the LLM for cruxes and did not consider any other metrics, e.g., involving next-token entropy, for identifying the cruxes.
The evaluations are only on forecasting and not any other kinds of reasoning tasks.
The introduction and fig 1 provide confusing descriptions of how the multiple rollouts are compared against each other to identify cruxes. Most of the writing is quite confusing.
This results do not seem very novel. There is previous research studying whether or not LLMs can anticipate the sub-tasks that need to be solved towards a larger problem, and the important factual information it might require to solve that problem. There is also research studying how well LLMs can summarize and identify the key points of their own reasoning.
Questions for authors
Is it possible to test how important a crux is using causal interventions where you change the result of a reasoning step and test how much that impacts the answer?
Can the authors write a comprehensive discussion section detailing the implications of their work and explaining how it provides new scientific insights into LLM behaviors (beyond the brief description in related works)?
Can the authors dig deeper into the when and why an LLM can or cannot identify the key future steps of its reasoning? For example, can the prompt be structured in a way that makes it easier for an LLM to identify cruxes?
Cruxes are a property of the differences between rollouts, not of any single rollout.
Causality can not verify Disagreement
We do not claim causality within a single rollout, nor would that be informative for identifying the differences between pairs of rollouts. Disagreement is not a causal question, so cannot inform nor validate disagreement between rollouts.
The reason we study disagreement between rollouts rather than interventions on a individual rollouts is because 1. disagreement across the entire rollout distribution has not been quantified before, and 2. observations about how pairs of rollouts differ does not risk pushing the model outside of its natural data manifold, as CoT interventions have to grapple with.
Examples are clearly labeled as differences: caption suggestions?
The examples are never claimed to change the outputs, they are clearly labeled as the differences between rollouts. Can the reviewer elaborate on why you interpreted them to be "examples of reasoning steps which cause the final output to change?" If you can elaborate on what led to the misunderstanding, then we can change the captions accordingly.
Our usage of 'crux' is consistent, and misrepresented in your interpretation
It is common English usage to refer to a crux as the difference between two people's arguments.
This aligns with line 13 of the abstract: "We take a crux to be a sub-question that a model’s rollouts disagree on, where changing its value may have altered the conclusion".
This is completely in line with with a deep analysis of the differences between many rollouts, which we repeatedly clarify is the object of study here.
Would additional clarification help readers?
Would it be helpful if we made an explicit analogy to a crux as the key difference between two people's arguments in both the abstract and introduction?
Common ground?
Can we at least agree that the root of our difference of opinions rests on:
We answer "No" to both questions: would you answer yes?