Candidate Sense Generation is the initial phase of Word Sense Disambiguation (WSD) that retrieves every potential meaning of an ambiguous clinical abbreviation from a pre-compiled sense inventory, such as the Unified Medical Language System (UMLS) Metathesaurus. For an acronym like 'MI,' this step generates a candidate list including 'Myocardial Infarction,' 'Mitral Insufficiency,' and 'Mental Illness' for subsequent contextual evaluation.
Glossary
Candidate Sense Generation

What is Candidate Sense Generation?
Candidate Sense Generation is the foundational retrieval step in clinical abbreviation disambiguation that compiles all possible meanings of an ambiguous acronym from a structured knowledge base before contextual scoring.
This retrieval process relies on exact string matching against concept unique identifiers (CUIs) and lexical variants stored in knowledge bases like SNOMED CT and RxNorm. The quality of candidate generation directly impacts disambiguation accuracy—an incomplete inventory guarantees failure, while overly broad retrieval increases computational cost during the attention-based scoring phase that follows.
Key Characteristics of Candidate Sense Generation
The initial retrieval phase that populates the disambiguation pipeline with all plausible meanings from a structured knowledge base, enabling subsequent contextual scoring.
Sense Inventory Lookup
The process of querying a pre-compiled knowledge base to retrieve all possible meanings for an ambiguous abbreviation. For clinical text, this inventory is typically derived from the Unified Medical Language System (UMLS) Metathesaurus, which aggregates over 200 source vocabularies.
- Input: The surface form 'MI'
- Output: A set of Concept Unique Identifiers (CUIs) including C0027051 (Myocardial Infarction) and C0026266 (Mitral Valve Insufficiency)
- Mechanism: Exact string matching against a normalized index of abbreviations and their long forms
Semantic Type Pre-Filtering
A pruning step that constrains the candidate set based on high-level UMLS Semantic Types before contextual scoring begins. This eliminates grossly implausible senses and reduces computational load.
- A mention in a 'Medications' section can filter candidates to only those with semantic type 'Clinical Drug' or 'Pharmacologic Substance'
- Removes candidates like 'Disease or Syndrome' or 'Diagnostic Procedure' from consideration
- Reduces the candidate set by 40-60% in typical clinical narratives, improving downstream precision
Lexical Variant Expansion
The generation of additional surface forms and synonyms for each candidate sense to improve the robustness of subsequent similarity scoring. A single CUI may have dozens of lexical variants.
- C0027051 (Myocardial Infarction) expands to: 'MI', 'heart attack', 'myocardial infarct', 'cardiac infarction', 'coronary occlusion'
- Crucial for handling: Clinical shorthand, typographical errors, and institution-specific jargon
- Leverages the MRCONSO table in UMLS, which maps each concept to all known string forms across source vocabularies
Knowledge Graph Traversal
An advanced candidate generation technique that traverses hierarchical relationships in the UMLS semantic network to include broader or narrower concepts as additional candidates.
- If 'ACE' maps to 'Angiotensin-Converting Enzyme Inhibitors', graph traversal can include child concepts like 'Lisinopril' and 'Enalapril'
- Uses PAR/CHD (parent/child) and RB/RN (broader/narrower) relationship types
- Enables the disambiguation system to resolve abbreviations to the correct level of granularity required by the downstream task, such as ICD-10-CM coding
Ambiguity Index Calculation
A quantitative measure of how polysemous an abbreviation is, calculated as the cardinality of its candidate sense set. This index drives triage logic in the disambiguation pipeline.
- Low Ambiguity (1-2 senses): 'CHF' almost always maps to 'Congestive Heart Failure' — fast-track to expansion
- High Ambiguity (10+ senses): 'MI' requires full contextual scoring across cardiology, neurology, and dermatology domains
- Extreme Ambiguity (50+ senses): 'CA' (Cancer, Calcium, Cardiac Arrest, Carcinoma, etc.) triggers section-header awareness and document-level context integration
Confusion Pair Pre-Identification
A proactive analysis that identifies the specific sense pairs most likely to be confused during scoring, based on co-occurrence statistics in the training corpus. This metadata is attached to the candidate set.
- Classic pair: 'MI' → Myocardial Infarction vs. Mitral Insufficiency (both cardiology, same semantic type)
- Metadata tag: Flags these candidates as requiring high-confidence contextual evidence for resolution
- Enables the downstream scoring model to apply contrastive attention mechanisms that focus on differentiating clinical features like 'troponin elevation' vs. 'regurgitant murmur'
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.
Frequently Asked Questions
Explore the foundational mechanisms of clinical abbreviation disambiguation, covering how systems retrieve and filter potential meanings from biomedical knowledge bases before contextual scoring.
Candidate Sense Generation is the initial retrieval phase in medical abbreviation disambiguation that queries a pre-compiled sense inventory—typically the Unified Medical Language System (UMLS) Metathesaurus—to enumerate all possible meanings of an ambiguous clinical acronym. When a system encounters an abbreviation like 'MI,' this step retrieves every known expansion, including 'Myocardial Infarction,' 'Mitral Insufficiency,' and 'Mechanical Intestinal Obstruction,' each identified by a unique Concept Unique Identifier (CUI). This process does not yet determine which meaning is correct; it simply builds the candidate set for subsequent contextual scoring. The quality of this generation directly impacts downstream accuracy, as a missing sense in the inventory guarantees a disambiguation failure regardless of how sophisticated the scoring model is.
Related Terms
Candidate sense generation is the critical first stage in resolving clinical ambiguity. Explore the core concepts that feed into and depend on this initial retrieval step.
Unified Medical Language System (UMLS)
The foundational sense inventory for candidate generation. UMLS integrates over 200 biomedical vocabularies, providing Concept Unique Identifiers (CUIs) and semantic types that serve as the target meanings for ambiguous abbreviations. A single abbreviation like 'CA' maps to multiple CUIs—'Carcinoma' (C0007097), 'Calcium' (C0006675), and 'California' (C1552032)—all retrieved during candidate generation.
Semantic Type Filtering
A pruning technique applied immediately after candidate retrieval. By constraining candidates to high-level UMLS categories, the system eliminates implausible senses before scoring. For example, when 'MI' appears in a Medications section, candidates with semantic type 'Clinical Drug' are retained while 'Disease or Syndrome' senses are deprioritized. This reduces the search space and improves downstream accuracy.
Contextual Embedding
The vector representation that enables candidate scoring. Models like ClinicalBERT generate dynamic embeddings where the same abbreviation receives different vectors depending on surrounding text. The embedding for 'CHF' in 'CHF exacerbation' is mathematically closer to the 'Congestive Heart Failure' sense embedding than to the 'Swiss Franc' sense, enabling precise disambiguation via cosine similarity.
Entity Linking
The downstream task that consumes disambiguated candidates. Once the correct sense is selected, entity linking grounds the mention to a unique identifier in a knowledge base. Key targets include:
- SNOMED CT Concept IDs for clinical findings
- RxNorm CUIs (RxCUIs) for medications
- ICD-10-CM codes for billing classifications This step transforms resolved text into structured, queryable data.
Confusion Pair Analysis
An error analysis methodology for refining candidate generation. By identifying the specific sense pairs a model most frequently confuses—such as 'MI' for 'Myocardial Infarction' versus 'Mitral Insufficiency'—engineers can augment the sense inventory with discriminative features or add targeted training examples. This analysis directly informs improvements to the candidate retrieval and scoring pipeline.
Clinical BERT
A family of transformer models pre-trained on clinical corpora like MIMIC-III that provide the contextual representations for candidate scoring. Unlike general-domain BERT, ClinicalBERT captures domain-specific co-occurrence patterns—understanding that 'q.d.' near 'tablet' likely means 'once daily' rather than 'every other day'. These models form the backbone of modern disambiguation architectures.

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