ReasoningFlow: Discourse Structures for Understanding LLM Reasoning Traces
Abstract: Large reasoning models (LRMs) produce reasoning traces with non-linear structures, such as backtracking and self-correction, that complicate the evaluation and monitoring of the reasoning process. We introduce ReasoningFlow, a framework that captures the discourse structures of LRM reasoning traces into fine-grained directed acyclic graphs (DAGs). We develop and validate our annotation schema through careful manual annotation of 31 traces (2.1k steps), achieving high inter-annotator agreement, then scale to automatic annotation of 1,260 traces (247.7k steps) spanning three tasks (math, science, argumentation) and five models (Qwen2.5-32B-Inst, QwQ-32B, DeepSeek-V3, DeepSeek-R1, GPT-oss-120B). By analyzing ReasoningFlow graphs, we find: (1) LRMs exhibit structurally similar traces, despite being trained from different base models and potentially non-overlapping post-training data. (2) ReasoningFlow reveals diverse fine-grained reasoning behaviors (e.g., local verification, self-reflection, and assumptions) that can be used for better reasoning trace monitorability. (3) In LRMs, most of the erroneous steps are not used to derive final answers. (4) Mechanistic causal dependencies between steps do not reflect the language-level discourse structure. We release the dataset and code in: https://github.com/jinulee-v/reasoningflow.
Paper Prompts
Sign up for free to create and run prompts on this paper using GPT-5.
Top Community Prompts
Explain it Like I'm 14
What this paper is about (big picture)
The paper introduces ReasoningFlow, a new way to โmap outโ how big AI models think when they show their step-by-step reasoning. Instead of seeing their thoughts as a straight line, ReasoningFlow treats them like a forward-moving flowchart with branches, checks, and corrections. This helps people judge how the model is thinking, not just whether the final answer is right.
The main questions the paper asks
- How can we describe an AI modelโs โthinking-out-loudโ trace in a clear, detailed, and consistent way?
- Can this description capture real behaviors like planning, checking work, changing course, and making assumptions?
- Do different models โthinkโ in similar shapes or patterns?
- How do mistakes in the middle of the reasoning affect the final answer?
- Do internal, model-based signals about what influenced what match the reasoning structure we see in the text?
How the researchers approached it
Think of an AIโs reasoning trace as a diary of thoughts while solving a problem. The authors turn this diary into a one-way map called a directed acyclic graph (DAG). You can picture it like a flowchart:
- Nodes are steps (short snippets of text).
- Edges are arrows showing how one step leads to or comments on another.
- โOne-wayโ means arrows only go forward in time (no loops back).
They defined 8 types of nodes (kinds of steps) to make the flowchart meaningful:
- Reasoning (the main thinking steps like calculation or deduction)
- Planning (what the model plans to do next)
- Reflection (self-checking or expressing confidence/uncertainty)
- Fact/Restatement (stating or re-stating facts)
- Assumption (trying out a โwhat ifโ idea that might be false)
- Example (testing with a specific case)
- Conclusion (the final answer)
- Note: the paper groups some of these as special cases of reasoning, but the above list reflects the full set.
They also defined 14 types of edges (kinds of arrows), such as:
- infer (this thought was logically derived from earlier steps)
- proceed/verify (planning to continue or check something)
- support/attack (later steps agreeing with or correcting earlier ones)
- reflection with sentiment (positive, uncertain, or negative self-evaluation)
To make sure this system is reliable, they:
- Manually labeled 31 traces (about 2,100 steps) and showed that two different annotators agreed a lot (high reliability).
- Then used AI to automatically label a much bigger set: 1,260 traces (about 248,000 steps) from math, science, and argument debates, across five models.
- They also rated the quality of steps (e.g., correctness for math/science or argument strength for debates) to study how structure connects to quality.
What they found and why it matters
Here are the most important findings, and why theyโre useful:
- Different reasoning models think in similar shapes
- Even though the models were trained differently, their reasoning traces had similar structural patterns (like how often they plan, infer, verify, or correct).
- Why it matters: This suggests there are common โgood habitsโ of reasoning that AI models tend to develop, which could guide training and evaluation.
- Fine-grained behaviors are visible and trackable
- The framework captures detailed behaviors like:
- Local verification: noticing and fixing a small mistake quickly (โWait, is that right? Let me recalcโฆ OK, hereโs the fix.โ)
- Self-reflection: judging a step as confident, unsure, or doubtful
- Assumptions: trying a โwhat ifโ branch (like proof by contradiction or exploring one option at a time)
- Why it matters: These behaviors help us monitor how the model thinks, not just what answer it gives.
- Local checking beats global checking
- Local verification (fixing small issues right away) happens more often than global verification (re-checking the entire solution at the end).
- When the model corrects something locally, the correction is more likely to be used to reach the final answer than the original (wrong) step.
- Why it matters: Encouraging quick, targeted self-checks could improve accuracy and efficiency.
- Self-reflection lines up with quality
- When the model says itโs confident (positive reflection), the step is more often correct/strong; when itโs uncertain or negative, the step is more likely weak or wrong.
- Why it matters: The modelโs own โfeelingsโ about steps can be a helpful signal for monitoring and guiding reasoning, like a built-in confidence meter.
- Many errors donโt damage the final answer
- Most wrong steps are either never used later or get ignored when the model reaches the final answer. Only a small share of mistakes actually cause a wrong final answer.
- Why it matters: Simply counting errors isnโt enough. We should track which errors feed into the final conclusion to judge real impact.
- Internal influence signals donโt match the text structure well
- A โmechanisticโ method (muting parts of the model to see how much earlier steps โcauseโ later ones) didnโt line up strongly with the human-annotated reasoning edges. Distance in time (how close steps are) explained a lot of the effect.
- Why it matters: Understanding reasoning needs both inside-the-model tools and outside, language-based structure. ReasoningFlow covers the language side and shows where gaps remain.
What this could change going forward
- Better monitoring and safety: If we can see when a model is planning, verifying, or making assumptionsโplus which steps actually feed into the answerโwe can catch problems earlier and focus on the most important parts of the trace.
- Smarter training: Since different models show similar โshapesโ of reasoning, training could intentionally teach useful patterns like local verification and clear planning.
- More fair and faithful evaluation: Instead of punishing any trace with any error, evaluators can focus on whether errors actually influence the final answer.
- Bridging the gap between text and internals: ReasoningFlow offers a human-readable map of reasoning. Combining it with mechanistic tools could lead to models whose inner workings line up better with what they โsayโ in their reasoning.
The authors released their dataset and code so others can build on this work. In short, ReasoningFlow gives us a clear, detailed map to understand and improve how AI models think through problems, not just whether they end up with the right answer.
Knowledge Gaps
Unresolved gaps, limitations, and open questions
The paper leaves the following concrete gaps and open questions that future work could address:
- Validate segmentation reliability: report inter-annotator agreement for node boundary segmentation itself (not only node/edge labels given a fixed segmentation), since sub-sentence splits are key to the schema.
- Quantify automatic segmentation quality: benchmark LLM-based segmentation against human segmentation (precision/recall on boundary placement, especially for coordination, discourse markers, and clause embedding).
- Improve edge labeling accuracy: edge detection/classification F1 (~0.65) is modest; provide per-label confusion matrices and targeted methods to fix the hardest relations (e.g., support vs. attack, execute vs. infer).
- Assess end-to-end annotation error propagation: measure how segmentation mistakes affect downstream node/edge labels and all subsequent analyses (local verification counts, error propagation rates, etc.).
- Expand manual gold coverage: the manually verified set (31 traces) is small and domain-limited; scale human adjudication across more tasks, models, and longer traces to robustly validate the pipeline.
- Calibrate LLM-as-a-judge correctness: replace or augment Gemini-based step validity judgments with human ratings and multiple-judge aggregation; report calibration, bias, and agreement statistics per domain.
- Validate ArgKP quality mapping: the node-to-AQR argument matching via LLM is a potential source of noise; quantify matching precision/recall, coverage, and the effect of mismatches on argument quality analyses.
- Report uncertainty: add confidence intervals/bootstraps for key findings (e.g., percentage of errors that propagate, self-reflectionโquality correlations, triplet distribution divergences).
- Test robustness to sampling: all traces used greedy decoding (temperature 0); measure how ReasoningFlow structures and findings change with temperature, nucleus sampling, and stochastic decoding.
- Examine prompt sensitivity: analyze how small changes to system prompts or reasoning instructions alter graph structures, node frequencies, and monitoring conclusions.
- Broaden task coverage: extend beyond math/science/argumentation to programming, theorem proving, law, multi-hop QA, commonsense, planning, and multi-modal reasoning to test schema generality.
- Evaluate multi-turn and tool-augmented settings: adapt and test ReasoningFlow for interactive dialogues, tool use (code, calculators, search), retrieval-augmented generation, and agents.
- Cross-lingual generalization: assess whether node/edge taxonomies transfer to non-English traces and whether annotation quality degrades across languages.
- Schema completeness: identify and add missing node/edge types (e.g., citations, uncertainty quantification, tool-trigger/result, contradiction resolution) observed in new domains.
- DAG sufficiency: the left-to-right DAG constraint forbids cycles; investigate whether cycles are needed to represent revision loops or mutual constraints in complex reasoning, and how to encode them.
- Overlapping spans: nodes are contiguous and non-overlapping, but premises can be discontinuous or overlapping; explore span graphs that allow overlapping spans when needed.
- Long-range dependencies: O(N2) potential edges remain challenging; quantify real runtime/memory costs and develop pruning, sparsification, or learned retrieval for edge discovery at scale.
- Predictive utility: test whether graph features (motifs, reflection sentiment, verification density) can predict final-answer correctness or faithfulness better than stepwise error rates alone.
- Interventional validation of โlocal verificationโ: go beyond correlation by perturbing traces (e.g., remove/replace corrections) or prompting for/against local checks to causally measure steering effects.
- Error propagation claims vs. annotation noise: re-estimate โonly 14.4% of errors propagateโ under human-verified edges and conclusions to check stability of the claim to labeling errors.
- Mechanisticโdiscourse alignment breadth: replicate the Thought Anchors comparison across multiple models, tasks, context lengths, and alternative mechanistic measures (causal tracing, mediation, attention patching).
- Control for distance confounds: model partial correlations between mechanistic scores and edges controlling for token distance, length, and lexical overlap to isolate genuine semantic dependencies.
- Baseline discourse frameworks: convert traces into RST or argumentation parses (even if imperfect) to quantify what ReasoningFlow adds over established discourse parsers on the same data.
- Temporal and training dynamics: track ReasoningFlow structures across training checkpoints or RL phases to study emergence and changes in planning, verification, and error handling.
- Faithfulness metrics: develop quantitative metrics of trace faithfulness that use ReasoningFlow paths (e.g., error-to-conclusion path integrity) and validate them against human judgments of faithfulness.
- Assumption evaluation: operationalize and score hypothetical reasoning (proof-by-contradiction, DFS) for plausibility and exhaustiveness; create benchmarks with human-annotated assumption scopes and outcomes.
- Generalization to closed-source and distilled models: systematically test whether schema statistics and findings hold for o1, Gemini, Claude, and distillations (R1-Distill, OpenThoughts).
- Cost and accessibility: release lighter, open annotators trained on ReasoningFlow labels and report their performance/cost trade-offs to make large-scale graphing feasible for the community.
- Reproducibility details: provide full prompts, hyperparameters, and random seeds for all annotation stages; publish per-item annotations and adjudication notes to enable exact replication.
Practical Applications
Immediate Applications
The following applications can be deployed now using the ReasoningFlow schema, dataset, and code, as well as straightforward extensions of the paperโs analysis findings.
- Application: Production monitoring of LLM reasoning traces
- Sectors: software/ML ops, AI safety, enterprise IT
- What: Instrument LLM โthoughtโ logs into ReasoningFlow DAGs to monitor local verification, self-reflection sentiment, assumption scopes, and which steps causally support final conclusions.
- Tools/Workflows:
- โReasoningFlow Dashboardโ that overlays node/edge labels on traces and highlights the minimal conclusion-supporting path.
- Alerts when unsupported or negatively reflected steps feed into conclusions.
- Assumptions/Dependencies: Chain-of-thought (CoT) access must be enabled or approximated (e.g., via open models or opt-in logging); automatic edge detection has moderate accuracy (EDC F1โ0.646), so high-stakes use needs human-in-the-loop review.
- Application: Safer stepwise evaluation and Process Reward Model (PRM) training
- Sectors: AI/ML, foundation model training
- What: Weight error detection by whether a step lies on the DAG path to the Conclusion node, reducing over-penalization of unused or negated errors.
- Tools/Workflows:
- PRM datasets labeled with ReasoningFlow edges; loss shaping that focuses on conclusion-supporting paths.
- Model selection that prefers traces showing local verification over post-hoc global verification.
- Assumptions/Dependencies: Requires access to intermediate traces and labels; annotation cost for large runs.
- Application: Prompting and policy templates that encourage local verification
- Sectors: software, agents, customer support, tutoring
- What: System prompts and decode policies that promote short โverify-correct-continueโ loops over end-only verification, leveraging the paperโs finding that local verification is more effective.
- Tools/Workflows:
- Decoding strategies that trigger brief verification after key computations (โverifyโ Planning nodes) and gate continuation on positive Reflection.
- Assumptions/Dependencies: Minor latency increase; needs trace capture or proxy indicators to ensure the behavior manifests.
- Application: Explainability overlays for end users
- Sectors: enterprise software, consumer assistants, education
- What: Visual โreasoning mapโ that shows the small set of steps used to derive an answer, flags assumptions, and shows self-reflection sentiment as confidence cues.
- Tools/Workflows:
- UI components that collapse unused branches, highlight support/attack relations, and display โassumption scopes.โ
- Assumptions/Dependencies: CoT visibility; privacy controls for storing traces.
- Application: Compliance and audit checks in regulated workflows
- Sectors: healthcare, finance, legal, public sector
- What: Gate conclusions unless every step on the supporting path is (a) valid or (b) formally reviewed; flag if any negatively reflected or unverified assumption connects to a decision.
- Tools/Workflows:
- โReasoningFlow-based compliance checkerโ integrated into decision support tools (e.g., clinical summaries, underwriting memos).
- Assumptions/Dependencies: Human oversight for ambiguous steps; organizational policies must accept discourse-structure audits.
- Application: Dataset curation and filtering for reasoning quality
- Sectors: AI/ML data engineering
- What: Select or weight training traces showing desired structures (e.g., frequent local verification, minimal unsupported restatements), and downweight traces where conclusions rely on negatively reflected steps.
- Tools/Workflows:
- โReasoningFlow Filterโ for CoT corpora; structural diversity sampling for training robust LRMs.
- Assumptions/Dependencies: Requires large-scale automatic annotation (costly with frontier models).
- Application: Debugging and root-cause analysis of LLM errors
- Sectors: software/ML engineering
- What: Triage failures by distinguishing unused, neglected, and faithfully propagated errors; focus remediation on faithful error paths.
- Tools/Workflows:
- Error heatmaps on DAGs; regression testing that specifically targets edges on conclusion paths.
- Assumptions/Dependencies: Consistent segmentation and edge inference; trace storage.
- Application: RAG and tool-use orchestration informed by structure
- Sectors: knowledge management, customer support, developer tools
- What: Route steps tagged as โexecute/verifyโ to tools (calculators, retrievers); drop or compress branches not feeding conclusions to save tokens and improve response time.
- Tools/Workflows:
- Agent controllers that invoke tools when Reflection is uncertain/negative and elevate compute only locally.
- Assumptions/Dependencies: Tool integration; reliable detection of Planning/Reflection nodes.
- Application: Education and tutoring feedback
- Sectors: education (math/science/argumentation)
- What: Visualize studentsโ (or the tutor-modelโs) reasoning DAGs; explicitly mark assumptions, self-checks, and supporting evidence paths to foster meta-cognition.
- Tools/Workflows:
- โReasoningFlow Tutor Viewโ for math/science problem solving and debate coaching.
- Assumptions/Dependencies: Classroom-friendly UIs; alignment with curricula.
- Application: Benchmarking and evaluation metrics
- Sectors: academia, benchmark maintainers
- What: New metrics that score the validity of conclusion-supporting subgraphs and the rate/effectiveness of local verification; structural similarity analyses across models/domains.
- Tools/Workflows:
- Leaderboard add-ons: โsupport-path correctness,โ โlocal verification density,โ โreflection-quality correlation.โ
- Assumptions/Dependencies: Agreement on segmentation conventions; accepted use in competitions.
- Application: Cross-check mechanistic metrics with discourse structure
- Sectors: interpretability research
- What: Use ReasoningFlow edges as a language-level ground truth to sanity-check attention-masking or anchor-based causal measures that can be confounded by distance.
- Tools/Workflows:
- Side-by-side curves (as in the paper) and error analysis to diagnose where mechanistic scores diverge from discourse relations.
- Assumptions/Dependencies: Access to model internals or proxies; open weights preferred.
- Application: Personal assistant transparency for daily life
- Sectors: consumer apps
- What: Let users expand an answer to see a compact, human-readable chain of supporting steps, with assumptions and self-confidence cues.
- Tools/Workflows:
- โWhy this answer?โ drawer showing the verified path and optional branches.
- Assumptions/Dependencies: UX constraints; privacy for stored sessions.
Long-Term Applications
These directions require further research, scaling, or integration beyond the current release (e.g., improved automatic annotation accuracy, optimized costs, or new training objectives).
- Application: Structure-aware training objectives and RL for reasoning
- Sectors: AI/ML
- What: Reinforcement learning and process supervision that explicitly rewards effective local verification, penalizes unsupported conclusion paths, and aligns self-reflection sentiment with step quality.
- Tools/Workflows:
- Structural reward models; imitation learning from high-quality DAGs; curriculum that gradually increases structural complexity.
- Assumptions/Dependencies: High-fidelity labels at scale; stability of structural signals across domains/models.
- Application: Certifiable reasoning for high-stakes decisions
- Sectors: healthcare, finance, law, safety-critical engineering
- What: Produce machine-checkable proofs that every edge on the support path is valid, combining discourse-level DAGs with formal or symbolic checks for key steps.
- Tools/Workflows:
- โSupport-path certificateโ attached to outputs; hybrid pipelines that verify compute-heavy steps with tools or human review before release.
- Assumptions/Dependencies: Formalization of step validators; organizational acceptance; latency budgets.
- Application: Reasoning-aware decoders and compute controllers
- Sectors: software/AI platforms, agents, robotics
- What: Real-time control policies that monitor Reflection and Verification nodes to adjust depth, branch, or backtrack (e.g., escalate compute when uncertainty spikes).
- Tools/Workflows:
- โReasoningFlow-aware decodingโ that allocates tokens to branches likely to influence conclusions and prunes unpromising ones.
- Assumptions/Dependencies: Robust online labeling (low-latency taggers); research on decoding-control stability.
- Application: Standards and policy for โreasoning trace disclosuresโ
- Sectors: policy/regulation, procurement, compliance
- What: Audit frameworks that require trace-structure evidence for critical AI outputs, specifying minimum checks (e.g., no negatively reflected step on support path).
- Tools/Workflows:
- Certification templates; procurement checklists; third-party auditing services using ReasoningFlow-like schemas.
- Assumptions/Dependencies: Regulatory consensus; privacy-preserving trace sharing; vendor cooperation.
- Application: Distillation of structure into smaller, specialized models
- Sectors: edge/enterprise AI
- What: Train compact taggers that predict node/edge labels without frontier APIs, enabling on-device or on-prem monitoring.
- Tools/Workflows:
- Teacher-student pipelines using the released dataset to supervise labelers; fine-tuning for domain-specific traces.
- Assumptions/Dependencies: Sufficient training data diversity; maintaining accuracy in constrained settings.
- Application: Hypothetical reasoning and DFS benchmarks/products
- Sectors: academia, assessment providers, agents
- What: New evaluations and agent behaviors that test and exploit proof-by-contradiction and depth-first assumption handling, as identified by ReasoningFlow.
- Tools/Workflows:
- Benchmarks scoring exhaustiveness and correctness of assumption-driven exploration; agents that explicitly bracket assumption scopes.
- Assumptions/Dependencies: Task design that rewards hypothetical reasoning; reliable detection of assumption patterns.
- Application: Mechanisticโdiscourse alignment research and training
- Sectors: interpretability, AI alignment
- What: Align internal causal pathways with discourse edges (e.g., encourage attention or routing to track support paths), reducing the gap observed in the paper.
- Tools/Workflows:
- Auxiliary losses tying token-level dependencies to ReasoningFlow edges; probes trained on DAGs.
- Assumptions/Dependencies: Access to model internals; risk of trade-offs with raw performance.
- Application: Robotics and planning with reasoning oversight
- Sectors: robotics, manufacturing, logistics
- What: Apply the schema to language-based planners to ensure action sequences are supported by valid preconditions and locally verified computations.
- Tools/Workflows:
- Planning monitors that pause execution when negative Reflection appears on the support path; auto-escalation to sensor/tool checks.
- Assumptions/Dependencies: Reliable mapping from natural-language plans to actions; integration with control loops.
- Application: Enterprise knowledge and policy engineering
- Sectors: corporate governance, risk management
- What: Extend ReasoningFlow-like structures to map and audit internal AI-generated policy rationales and argumentation in strategy documents.
- Tools/Workflows:
- Argument maps showing support/attack chains and assumption dependencies for decisions.
- Assumptions/Dependencies: Adapting the schema from LLM traces to longer, mixed-origin documents; cultural adoption.
- Application: Adaptive tutoring and assessment of meta-cognition
- Sectors: education technology
- What: Evaluate and train studentsโ reasoning by scoring structure (verification density, quality-aligned reflection) alongside correctness; personalize remediation.
- Tools/Workflows:
- โStructural reasoning scoresโ embedded in LMSs; targeted hints when reflection is negative/uncertain.
- Assumptions/Dependencies: Validity studies with human learners; fairness considerations.
- Application: Automated governance guards
- Sectors: platform safety, content moderation
- What: Policy engines that block or downrank outputs whose conclusions are supported by paths containing invalid, uncertain, or negatively reflected nodes.
- Tools/Workflows:
- Pre-deployment tests that simulate adversarial prompts and inspect structural error propagation.
- Assumptions/Dependencies: Low false-positive rates; transparency to users and developers.
Notes on dependencies across applications:
- Access to reasoning traces is essential; closed models that redact CoT diminish feasibility unless replaced by open or distilled LRMs.
- Current automatic annotation is moderately accurate and costly; scaling requires specialized, smaller taggers trained on the released data and/or human oversight for sensitive uses.
- Data governance is required since traces may contain sensitive information; storage and audit trails must comply with privacy regulations.
Glossary
- Argumentation trees: Tree-structured representations of argumentative relations where premises recursively support a main claim. "single-root argumentation trees"
- Autoregressive LLMs: Models that generate tokens sequentially, conditioning each next token on previous outputs. "in autoregressive LLMs"
- Depth-first search (DFS): A search strategy that explores one branch to completion before backtracking to explore alternatives. "depth-first search (DFS): when encountering mutually exclu- sive branches, assuming one option at a time in- stead of considering all options simultaneously."
- Directed acyclic graph (DAG): A directed graph with no cycles, used here to encode step-to-step discourse relations. "a directed acyclic graph with 8 node types and 14 edge types."
- Entailment graphs: Graphs that link statements via logical support or entailment relations. "reasoning traces were commonly viewed as entailment graphs"
- Greedy decoding: Inference that selects the highest-probability token at each step without sampling. "We use greedy decoding (temperature 0) for all models."
- Hyperedges: Edges in a hypergraph that can connect more than two nodes; used to model complex paragraph-level links. "with verification and backtracking hyperedges."
- Inter-annotator agreement: A reliability measure of consistency between human annotatorsโ labels. "validate with inter-annotator agreement analysis."
- JensenโShannon divergence (JS-Div): A symmetric information-theoretic distance between probability distributions. "Jensen-Shannon Divergence of triplet distributions between models."
- KL-divergence: KullbackโLeibler divergence; a measure of how one probability distribution differs from another. "the causal dependency score is defined as the average log KL-divergence"
- Krippendorff's alpha: A statistical coefficient assessing the reliability of categorical annotations across annotators. "with Krippendorff's a > 0.8"
- Large Reasoning Models (LRMs): LLMs trained or adapted to produce extended, structured reasoning traces. "Large Reasoning Models (LRMs; e.g., DeepSeek- R1 (Guo et al., 2025))"
- LLM-as-a-judge: The practice of using an LLM to evaluate or score the correctness or quality of outputs. "we employ LLM- as-a-judge (Gemini-3-Flash)"
- Masking attentions: An intervention that disables specific attention connections to probe causal dependencies between steps. "by masking attentions."
- Mechanistic interpretation: Analysis focused on internal model behavior and causal dependencies rather than surface text. "Mechanistic interpretation of trace structures."
- Precision-Recall curve: A plot of precision versus recall across thresholds for evaluating binary predictions. "Precision-Recall curve of using Thought An- chors' scores to predict ReasoningFlow edges."
- Principal Component Analysis (PCA): A dimensionality-reduction technique used to identify major axes of variation. "Principal Component Analysis (PCA)"
- Process Reward Models: Models that score or classify intermediate steps in a reasoning process to evaluate stepwise quality. "often using classifiers (Process Reward Models)"
- Proof-by-contradiction: A reasoning method that assumes the negation of a claim and derives a contradiction to prove the original claim. "proof-by-contradiction"
- Rhetorical Structure Theory (RST): A framework that models discourse via hierarchical relations between text spans. "Rhetorical Structure The- ory (RST) builds hierarchical discourse structures"
- Thought Anchors: A method that quantifies causal dependencies between reasoning steps using attention-masking perturbations. "Thought Anchors (Bogdan et al., 2025) proposes measuring the causal dependency"
Collections
Sign up for free to add this paper to one or more collections.