Skip to content

AI & ML OverviewΒΆ

This document describes the AI and machine learning components used in the Pebble Business Orchestrator for intent recognition, entity extraction, and process intelligence.


AI Capabilities SummaryΒΆ

Capability Model Type Purpose
Intent Recognition Transformer (BERT/LLM) Routing emails to Sales, Ops, or Tenders
Business Entity Extraction NER / LLM Extracting GST, PAN, CIN, and Order IDs
Tender IQ (OCR) Deep Learning Extracting NIT details and dates from PDFs
Sentiment & Saliency NLU Identifying high-priority/urgent leads

πŸ› οΈ Execution Context: Cloud vs. LocalΒΆ

Pebble supports both cloud-native and private, on-premise AI execution.

Context Recommended Stack Best For
Cloud Azure OpenAI / Google Gemini High accuracy, zero infra management.
Local (Private) Ollama (Llama 3 / Mistral) High privacy, zero per-token cost, offline ops.

1. Intent Classification (The Brain)ΒΆ

PurposeΒΆ

Automatically classify incoming emails into specific operational streams (Sales, Logistics, Quality, Tenders) to ensure they land on the correct Kanban board.

Model HierarchyΒΆ

graph TD
    A[Incoming Email] --> B{Intent Classifier}
    B --> C[Sales enquiry]
    B --> D[Logistics/Dispatch]
    B --> E[Tender/NIT]
    B --> F[General/Unclassified]

    C --> C1[New Quote]
    C --> C2[Follow-up]

    D --> D1[Tracking Query]
    D --> D2[Dispatch Proof]

Model OptionsΒΆ

Model Type Best For
RoBERTa-base Transformer High accuracy intent detection (Default)
DistilBERT Transformer Low-latency real-time triage
SetFit Few-Shot Training on very small datasets (<50 samples)

2. Business Entity Extraction (NER)ΒΆ

PurposeΒΆ

Extract structured business identifiers to enable one-click synchronization with Odoo, Zoho, and Focus RT.

Critical EntitiesΒΆ

Entity Regex/Model Purpose
GST Number Pattern Match Validating tax compliance (Stage 3)
CIN/PAN Pattern Match Master data verification
Order ID Contextual NER Linking emails to ERP orders
Dates (NIT) DateParser Tracking tender bidding deadlines

3. Tender IQ (OCR & Vision)ΒΆ

PurposeΒΆ

While the core of Pebble is email orchestration, Phase 3 involves deep intelligence for Tenders which often arrive as scanned documents.

PipelineΒΆ

  1. OCR Engine: Azure AI Document Intelligence or Tesseract 5.
  2. Layout Analysis: Identifying tables of "Item Codes" and "Quantities".
  3. Similarity Engine: Comparing current NIT specs against historical "Closed Won" tender results.

4. Confidence & Human-in-the-LoopΒΆ

Pebble follows an "Augment, Don't Automate" philosophy. Every AI decision includes a confidence score that determines UI behavior.

Confidence UI Behavior
High (>90%) Card auto-placed; Label applied with green check.
Medium (70-90%) Card placed; "Suggested Intent" shown for confirmation.
Low (<70%) Card sent to "Unclassified" queue for manual triage.

5. Model Training & EvaluationΒΆ

Continuous Learning LoopΒΆ

flowchart LR
    A[Production] --> B[Log Predictions]
    B --> C[User Moves Card]
    C{Correction?}
    C -->|Yes| D[Log as Negative Sample]
    C -->|No| E[Log as Positive Sample]
    D & E --> F[Retrain Intent Model]
    F --> G[Deploy Updated Weights]

← Back to Home | View MVP Scope