SEM-004 · Semantic Demand

Disambiguate homonyms and polysemy

• Baseline
• IF
• OR
• THEN
• ELSE

The decision

• IF
  • the same wording can refer to different concepts, entities, or tasks
• THEN
  • create sense labels and exclusions before clustering
• ELSE
  • use the unambiguous concept

Primary metric

wrong-sense rate

Guardrail

query misclassification

Reason

Makes the decision explicit, measurable, and reversible where possible.

LAKA levels

• Baseline

Operators

• IF
• OR
• THEN
• ELSE

Governs gates

• demand

Source

04-IF-ELSE-AND-OR-RULEBOOK.md — SEM-004 — Disambiguate homonyms and polysemy

The other eleven rules in Semantic Demand

• SEM-001 Start from parent concepts IF an offer lacks a mapped semantic territory Baseline
• SEM-002 Expand through subtypes IF a parent concept contains meaningful narrower types with distinct tasks Baseline
• SEM-003 Normalize synonyms and paraphrases IF different phrases express the same sense and dominant task Baseline
• SEM-005 Model modifiers as facets IF terms vary by price, material, size, audience, platform, location, time, or other attributes Baseline
• SEM-006 Use co-occurrence as context IF a term commonly appears near the topic but is not itself the user’s target Minor
• SEM-007 Map entities and relations IF the task depends on named things and how they connect Major
• SEM-008 Map query fan-out without page fan-out IF one broad task implies several supporting questions Major
• SEM-009 Triangulate demand evidence IF a candidate appears in only one tool or source Baseline
• SEM-010 Do not equate zero tool volume with zero demand IF a query has low or zero reported volume but appears in first-party or customer evidence Baseline
• SEM-011 Attach time state IF facts, prices, availability, standards, laws, events, or recommendations can change Structural
• SEM-012 Model emerging demand separately IF a new technology, regulation, event, or behavior has weak historical search data but strong causal evidence Paradigm