A Concept Bottleneck Model (CBM) is an interpretable neural network architecture that first predicts a set of human-specified, high-level concepts from the input and then uses only those concept scores to make the final prediction. This architectural constraint forces the model to base its reasoning on semantically meaningful attributes, such as 'wing color' or 'bill shape' for bird classification, rather than opaque pixel correlations.
Glossary
Concept Bottleneck Models

What is Concept Bottleneck Models?
A model architecture that predicts human-specified concepts before making a final decision, enabling direct intervention and concept-level explanation.
The key operational advantage of CBMs is test-time intervention. Because the decision logic is mediated through an interpretable concept layer, a human operator can directly edit incorrect concept predictions—for example, correcting a misidentified 'bone spicule' in a medical image—and the downstream prediction will update accordingly, without retraining. This makes CBMs uniquely suited for high-stakes domains requiring human oversight and auditability.
Key Features of Concept Bottleneck Models
Concept Bottleneck Models (CBMs) enforce a strict architectural separation between concept learning and task prediction, enabling direct human intervention and concept-level explanation.
Two-Stage Prediction Pipeline
CBMs decompose prediction into two distinct stages: first, a concept encoder maps raw inputs to a set of human-specified concept scores; second, a task predictor uses only those concept scores to make the final decision. This bottleneck ensures the model cannot bypass the interpretable concept layer, forcing all reasoning through human-understandable attributes.
Human-Intervention Capability
A defining advantage of CBMs is the ability for domain experts to directly edit concept predictions at test time without retraining. If a model mispredicts a concept (e.g., 'wing color' for a bird classifier), a human can override that value, and the corrected concept score propagates to improve the final task prediction. This enables real-time collaborative decision-making between humans and AI.
Concept-Level Explainability
Unlike post-hoc methods that approximate explanations, CBMs provide inherent, faithful explanations by design. The final prediction is a direct function of the predicted concept scores, so the reasoning is fully transparent: 'This X-ray was classified as malignant because the model detected spiculated margins and irregular shape.' Each concept's contribution to the final decision can be traced and quantified.
Test-Time Intervention Accuracy
Research demonstrates that human interventions on CBMs can dramatically improve task accuracy even when concept predictions are imperfect. In medical imaging benchmarks, allowing radiologists to correct a small subset of mispredicted concepts has been shown to boost diagnostic accuracy by over 10%, making CBMs particularly valuable in high-stakes domains where errors are costly.
Concept Dataset Requirements
CBMs require training data annotated with concept labels in addition to task labels. For each input, human annotators must specify the presence or absence of predefined concepts. This annotation cost is a key trade-off: while it enables interpretability and intervention, it demands domain expertise and careful concept ontology design to ensure the chosen concepts are both predictive and meaningful.
Sequential vs. Independent Bottlenecks
Two architectural variants exist: the independent bottleneck, where concepts are predicted simultaneously without inter-concept dependencies, and the sequential bottleneck, where concepts are predicted in a causal order. The sequential variant can model relationships between concepts (e.g., 'bone fracture' depends on 'bone visible'), improving accuracy but requiring a predefined concept hierarchy.
Frequently Asked Questions
Clear answers to common questions about Concept Bottleneck Models, an interpretable architecture that predicts human-understandable concepts before making a final decision.
A Concept Bottleneck Model (CBM) is an interpretable deep learning architecture that first predicts a set of human-specified, high-level concepts from raw input data, and then makes its final prediction using only those concept scores, never directly from the raw features. The architecture enforces a strict information bottleneck: the model must express everything it knows about the input in terms of concepts a human can understand. For example, a bird classifier would first predict concepts like 'has a red wing,' 'has a pointed beak,' and 'has a forked tail' from the image, then predict the bird species solely from those concept activations. This two-stage design—concept encoder followed by concept-to-label predictor—enables direct human intervention, where a clinician or domain expert can manually correct mispredicted concepts and observe how the final prediction changes in real time.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Concept Bottleneck Models belong to a class of inherently interpretable architectures. These related terms cover the core mechanisms, intervention techniques, and evaluation methods that define the CBML paradigm.
Concept Annotation
The process of labeling raw input data with human-specified, high-level concepts to train the first stage of a CBM. Unlike traditional labeling which only provides a final class, annotators mark the presence or absence of intermediate attributes.
- Dense annotation: Every concept is labeled for every sample
- Sparse annotation: Only a subset of concepts are labeled, requiring multi-modal training
- Uncertainty: Annotator disagreement is captured as a soft probability rather than a hard binary
Test-Time Intervention
A defining capability of CBMs where a human operator or automated policy can directly edit the predicted concept scores before the final prediction is made. This allows real-time correction of model errors without retraining.
- Hard intervention: Manually flipping a concept from 'absent' to 'present'
- Soft intervention: Adjusting the continuous probability of a concept
- Policy-based intervention: A rule engine automatically overrides concepts based on safety constraints
Concept Completeness
A metric evaluating whether the bottleneck layer captures all necessary information for the downstream task. An incomplete concept set forces the model to encode residual information outside the bottleneck, defeating interpretability.
- Completeness score: Measured by training a separate model on the concept scores and comparing its accuracy to the original CBM
- Residual fitting: Detecting if the final layer relies on information not present in the concept scores
Concept Leakage
A failure mode where the concept predictor inadvertently encodes protected attributes or shortcut features into the concept scores, bypassing the intended semantic meaning. For example, a 'stripes' concept detector might unintentionally encode zebra texture as a proxy for animal class.
- Mitigation: Adversarial training to remove sensitive information from the concept layer
- Detection: Probing classifiers trained to predict protected attributes from concept scores
Sequential CBMs
An architectural variant where concepts are organized into a hierarchical dependency graph rather than a flat set. The model predicts parent concepts first, then conditions child concept predictions on them.
- Causal ordering: Concepts follow a directed acyclic graph (DAG)
- Benefit: Prevents the model from using a child concept to predict its parent, enforcing logical consistency
- Example: Predicting 'has wings' before 'can fly'
Concept Activation Vectors (CAVs)
A closely related interpretability technique that tests whether a pre-trained neural network internally represents a human-specified concept, without requiring architectural modification. CAVs are the linear direction in activation space that separates examples of a concept from random counterexamples.
- TCAV score: The fraction of a target class's activations that are positively influenced by the concept direction
- Difference from CBMs: CAVs probe an existing black-box model; CBMs enforce concept learning by design

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us