Topic

Natural Language Processing (NLP)

All digests tagged Natural Language Processing (NLP)

Processing Documents: Jev vs OSS Models thumbnail

· 16:48

Processing Documents: Jev vs OSS Models

This video compares several model architectures (Jev, Quen, Leia, Jeff) for automating decision-making and classification tasks within document processing pipelines. The core finding is that the open decoder model, Quen, performs remarkably close to the generalized classifier, Jev, across various tasks (language detection, document classification, document routing). The approach demonstrates that robust classification can be achieved without requiring pre-training on specific labels, making it highly valuable for building flexible, automated document pipelines.

Key takeaways

  1. Quen's Performance in Classification

    The Quen decoder model, which is a standard Language Model (LM) and not specifically trained for classification, showed accuracy very close to Jev in tasks like language detection and document routing, suggesting its utility for general document understanding.

  2. Model Architecture Comparison 7:16

    Jev is a generalized classifier trained with reinforcement learning, optimized for confidence scoring. Quen is a decoder LM. Leia and Jeff are encoder models (Leia predicts a mask token; Jeff is good for entity/relation extraction). While encoders are smaller and easier to fine-tune, they were less accurate than the decoders in this demonstration.

  3. Document Processing Tasks Covered

    The models were tested on five key document pipeline tasks: Language Detection (using Lingua as baseline), Orientation Detection (using Tesseract as baseline), Document Classification, Document Splitting, and Document Routing/Triage.

Watch on YouTube Full article

From Scratch to SOTA: Training a 3B State-Space Vision Model — Krishna Prasad Srinivasan, Sarvam thumbnail

· 21:09

From Scratch to SOTA: Training a 3B State-Space Vision Model — Krishna Prasad Srinivasan, Sarvam

Sarvam introduced a 3 billion parameter (3B) State-Space Vision Language Model (VLM) designed for document AI, achieving state-of-the-art (SOTA) performance while being small enough to run on a single GPU. The model is notable for its use of a State Space Model (SSM) backbone instead of a traditional Transformer, which efficiently handles the quadratic complexity of long documents. The training process is a sophisticated four-stage curriculum, covering 13 trillion tokens across English and 22 Indian languages, and includes a proprietary data engine and machine-checkable reinforcement learning (RL) for scalable OCR correctness.

Key takeaways

  1. SOTA Document AI Performance

    The 3B parameter model achieves SOTA in document AI, claiming to beat models 100 times larger in size.

  2. Architectural Innovation (SSM) 3:30

    The model uses an SSM backbone instead of a Transformer to manage the high compute costs associated with quadratic attention ($L^2$) when processing long documents (up to 10,000 visual tokens).

  3. Comprehensive Training Curriculum 6:00

    Training involves four stages: 13T token pre-training (text), 300M image-text pairs (continual pre-training), 100M OCR samples (SFT), and RL using machine-checkable unit tests for rewards.

  4. Sovereign Capability 2:30

    The entire model building, data, compute, and training were done end-to-end in India, addressing the lack of machine-readable data for Indian languages.

Watch on YouTube Full article

What is Jev? The AI that Can't Talk Back (and why that's a good thing) thumbnail

· 33:02

What is Jev? The AI that Can't Talk Back (and why that's a good thing)

Jev is a new general-purpose AI classifier from TypeSafe that reads complex text and outputs only a single, predefined choice, eliminating the need for generative text. This capability allows developers to solve 'semi-deterministic' problems—those requiring judgment but yielding structured outcomes—at a fraction of the cost and speed of traditional Large Language Models (LLMs). The video outlines four architectural patterns for integrating Jev into existing software, positioning it as a crucial new primitive alongside deterministic code and LLMs.

Key takeaways

  1. Jev's Core Functionality

    Jev is a classifier that takes complex text input but is restricted to selecting from a predefined list of possible answers, making it fundamentally different from LLMs that generate sentences. This restriction is its primary advantage.

  2. Market Adoption and Value

    Jev was the fastest-adopted model in Vercel's AI gateway history, suggesting that the ability to classify cheaply and quickly is a highly valuable, unmet need in the industry.

  3. The Power of Classification 2:00

    Jev enables 'semi-deterministic' processes—where judgment is required (e.g., assessing customer dissatisfaction) but the output is a simple choice (e.g., 'High Risk,' 'Low Priority').

  4. Cost and Speed Advantage 22:00

    Jev offers massive cost and speed gains compared to LLMs. For example, one developer reported a 34x cost reduction and six times speed increase when using Jev for tax document classification.

  5. Architectural Patterns 26:40

    Jev can be used in four ways: 1) Classifying messy input for existing software; 2) Acting as a filter for large problem spaces (e.g., immunology research); 3) Choosing the next step in an AI workflow (outer loop orchestration); and 4) Interpreting user intent in real-time interfaces (e.g., spreadsheets).

Watch on YouTube Full article

Stop Chunking Like It's 2022 — Yuval Belfer, AI21 Labs thumbnail

· 18:01

Stop Chunking Like It's 2022 — Yuval Belfer, AI21 Labs

This talk challenges the fixed-chunking paradigm in Retrieval-Augmented Generation (RAG) systems. The core claim is that there is no single optimal chunk size; the correct size is query-dependent. The speaker proposes 'multiscale indexing,' which involves duplicating the corpus and chunking it at multiple window sizes. At retrieval time, all resulting indices are queried, and the results are merged using Reciprocal Rank Fusion (RRF), achieving significant recall improvements (20-40%) over fixed-size methods. This approach increases memory usage but maintains low latency overhead.

Key takeaways

  1. Chunking is Query-Dependent, Not Fixed 0:07

    The optimal chunk size varies drastically based on the query type. For example, a highly focused question (e.g., 'Jerry's favorite church') performs best with smaller chunks, while a broad, narrative question (e.g., 'who does Jerry describe as his nemesis') requires larger context windows to capture the answer spread across a scene. (7:07)

  2. Multiscale Indexing is the Solution 0:10

    Instead of committing to one chunk size, the system should index the corpus at multiple window sizes (multiscale indexing). At query time, all these indices are queried, and the resulting rankings are combined using Reciprocal Rank Fusion (RRF). (9:59)

  3. Significant Performance Gains 0:10

    The gap between the performance of the optimal 'oracle' chunk size and any single fixed choice (e.g., 512 tokens) can cost 20% to 40% of recall. The proposed method closes this gap. (9:59)

Watch on YouTube Full article

Putting Claudes "AI Slop" Solution to the Test thumbnail

· 7:01

Putting Claudes "AI Slop" Solution to the Test

The video provides a critical deep dive into the current state of AI product development, focusing heavily on the necessity of rigorous, data-driven evaluation (Evals) over relying on vendor demos or vague prompts. The speaker critiques common AI pitfalls, such as 'mannered prose' and the use of 'slop' in system prompts. For build engineers, the core message is to build small, realistic evaluation datasets and test candidate models against specific, failure-critical use cases (e.g., OCR, structured output) rather than relying on general benchmarks.

Key takeaways

  1. Prioritize Specificity Over Flowery Language 2:30

    The speaker critiques 'mannered prose' (e.g., 'the point earns its keep'), arguing that AI output should use direct, literal statements rather than metaphors or flourish, which are imprecise and confuse the reader. [00:02:30]

  2. Build Custom Evaluation Datasets (Evals)

    To accurately compare AI models, one must create a small evaluation set using data realistic to the specific use case (e.g., tables, scanned images, documents with stains). Leaderboards and vendor demos are insufficient because they do not test against proprietary failure modes. [00:08:20]

  3. System Prompts Must Be Precise 3:20

    When using system prompts or in-context examples, the goal should be to guide the model toward a specific, measurable output format (e.g., structured JSON with named fields) rather than relying on general instructions. [00:03:20]

Watch on YouTube Full article

"My name is... my name is...": A Linguistic Map for Voice Agents — Midam Kim, ServiceNow thumbnail

· 15:05

"My name is... my name is...": A Linguistic Map for Voice Agents — Midam Kim, ServiceNow

Midam Kim presents a linguistic framework for diagnosing failures in voice AI, arguing that these failures are not isolated bugs but structured issues. She proposes that human communication is a 'joint activity' involving the continuous updating of a 'mental model.' The framework maps this process onto two channels (listening and speaking) and four interdependent levels: sounds, words, interaction, and mental model. Successful voice AI requires holistic orchestration across all these layers, rather than optimizing components (like ASR or TTS) in isolation.

Key takeaways

  1. Voice AI is a Joint Activity 5:00

    Human communication is a joint activity where both parties contribute sounds and words, continuously updating a shared mental model. Voice AI systems must replicate this joint nature to be effective.

  2. The Linguistic Framework 11:54

    The system must be analyzed across two channels (listening/speaking) and four interdependent levels: sounds, words, interaction, and mental model. Failure in one area (e.g., STT failure at the sound level) impacts the entire system.

  3. Mental Model Accumulation

    Unlike text chat where history remains visible, in voice interactions, sounds and words vanish. The only persistent element that matters for user satisfaction is the user's accumulating mental model.

  4. System Adaptability is Key

    The system must be designed to be dynamic, adapting to context, emotion, and language change over the course of the call, rather than functioning as a static pipeline.

Watch on YouTube Full article

I Monitored Crime Audio. Voice Agents Scare Me More. — Sumanyu Sharma, Hamming AI thumbnail

· 16:04

I Monitored Crime Audio. Voice Agents Scare Me More. — Sumanyu Sharma, Hamming AI

The presentation compares the monitoring of decentralized, hyper-local crime data (Hamming's initial work) with the rapidly scaling, centralized risks of conversational voice agents. While voice AI is advancing rapidly, reliability remains the primary blocker for large-scale deployment. The speaker emphasizes that because voice agents are centralized, a single prompt or architectural change can have a massive 'blast radius.' He advocates for a continuous monitoring loop—including deep manual analysis, frequency/severity prioritization, and adversarial red teaming—to mitigate risks like unauthorized actions, incorrect information provision, and the leakage of PHI/PII.

Key takeaways

  1. Voice Agents vs. Crime Monitoring 7:12

    Crime incidents are generally hyper-local and decreasing, while voice agent usage is centralized and rapidly increasing, potentially handling a trillion calls annually. This centralization means a single failure point can impact millions of users.

  2. The Scale of Risk 8:43

    If a 1% error rate is assumed across annual calls, this equates to 10 billion potential bad interactions. In practice, monitoring 10,000 agents shows an error rate closer to 10%, manifesting as skipping eligibility checks or providing incorrect information.

  3. The Continuous Improvement Loop 11:44

    Fixing voice agent reliability requires a structured loop: Identify problems, prioritize by frequency and severity, understand the fix, execute the change, verify it hasn't caused regressions, and continue monitoring in production.

Watch on YouTube Full article

Recursive Self-Improvement: from Auto Research to Superintelligence — Richard Socher, Recursive thumbnail

· 1:33:27

Recursive Self-Improvement: from Auto Research to Superintelligence — Richard Socher, Recursive

The discussion centers on the concept of Recursive Self-Improvement (RSI) and the 'Eureka Machine'—a superintelligence capable of automating the process of invention itself. Richard Socher details how AI is moving beyond simple pattern recognition to self-directed research, significantly accelerating scientific and technological discovery across fields like physics, chemistry, and biology. Technically, the conversation covers the evolution of AI architectures (from manual feature engineering to Transformers), the critical role of hardware optimization (e.g., NVIDIA GPU kernels), and the complex challenges of AI alignment, reward hacking, and open-ended safety protocols.

Key takeaways

  1. The Eureka Machine and RSI 2:20

    The Eureka Machine is envisioned as a superintelligence that can be given any goal and will autonomously generate inventions for humanity, accelerating research in science and technology.

  2. AI's Self-Improvement Cycle 12:20

    The next major step in AI is RSI, where the AI automates its own research process (ideating, implementing, and validating ideas), leading to a self-improving system.

  3. Hardware and Physical Constraints 17:20

    The timeline for AGI is constrained not just by algorithms, but by physical limitations, including the availability of GPUs, semiconductors, and the energy efficiency of computation (e.g., comparing human brain efficiency to current chips).

  4. Safety and Alignment Challenges 28:20

    Current safety mechanisms like Constitutional AI are insufficient because they are prone to reward hacking and failure to understand human intent. Better alignment requires addressing the difference between what is 'said' and what is 'meant.'

Watch on YouTube Full article

How to build with Gemini 3.5 Transcribe thumbnail

· 4:50

How to build with Gemini 3.5 Transcribe

Google DeepMind launched Gemini 3.5 Transcribe, an LLM-based transcription model available via both the Interactions API and the Live API. This model significantly enhances accuracy by correctly transcribing complex data types—such as email addresses, phone numbers, and mixed units of measurement—and maintaining high performance across over 85 supported languages, even when language codes are set to English.

Key takeaways

  1. LLM-Based Transcription Model

    The model's LLM foundation allows it to handle complex data structures and context better than traditional transcription models. For example, it can correctly identify and edit email addresses even if spoken phonetically (e.g., 'tosten at google.com').

  2. Handling Complex Data Types 2:00

    Gemini 3.5 Transcribe accurately recognizes specific formats, including US phone numbers and international variations (e.g., Singapore's 8-digit format). It can also correctly interpret units of measure (e.g., meters vs. centimeters).

  3. Multilingual and Customization Support 0:40

    The model supports over 85 languages, automatically recognizing spoken language even if language hints are set to English. Accuracy can be further improved by providing custom vocabulary (e.g., names of people in a meeting) or setting specific language codes.

Watch on YouTube Full article

How Claude's Text Watermarking Works thumbnail

· 47:47

How Claude's Text Watermarking Works

This video provides a deep technical explanation of how Anthropic's text watermarking for Claude models operates. The technique modifies the standard next-token sampling process by introducing determinism using a secret 'watermarking key.' Instead of relying purely on random probability distribution (e.g., via softmax and random choice), the model uses specialized functions and a tournament sampling method to ensure that certain token choices are predictable, making the generated text traceable. Detection is achieved by applying these same watermarking functions across the entire text and calculating an average score against a defined threshold.

Key takeaways

  1. Watermarking Location 0:24

    The watermark is applied at the *sampling* stage of the LLM generation process, not within the core model weights. This means existing LLMs can implement this feature without requiring full retraining or modification of the underlying model architecture. (24:45)

  2. Deterministic Sampling 0:16

    The watermarking mechanism converts standard random sampling into a deterministic process by using a secret 'watermarking key' and previous tokens to derive a fixed random seed, ensuring that the same input always yields the same sequence of watermarked tokens. (16:19)

  3. Tournament Sampling 0:36

    To make detection efficient, the process uses 'tournament sampling.' Instead of simple random choice, plausible next tokens are paired up and compared using multiple specialized watermarking functions ($G_1, G_2, ext{etc.}$), which determines the final selected token. (36:36)

  4. Detection Method 0:47

    Watermark detection is performed by running the text through the same set of watermarking functions and calculating an average score across all positions. If this average score exceeds a specific threshold, the text is flagged as watermarked. (47:13)

Watch on YouTube Full article

How builders at YC Startup School are using Gemini & Google AI thumbnail

· 2:05

How builders at YC Startup School are using Gemini & Google AI

Founders and students at the YC Startup School demonstrated diverse applications of Google AI tools, including Gemini and Gemma. Use cases ranged from leveraging Gemini 3.1 Flash for multilingual document parsing (e.g., international receipts) to utilizing AlphaFold for visualizing bacterial mutations related to antibiotic resistance research. The speakers highlighted the efficiency and context window capabilities of models like Gemini Flash for complex tasks.

Key takeaways

  1. Multilingual Document Parsing 0:25

    Gemini 3.1 Flash is used to parse international receipts from various locations (e.g., Japan, Korea), demonstrating robust multilingual capabilities.

  2. Antibiotic Resistance Research 0:37

    AlphaFold is employed to visualize and study different bacterial mutations, supporting global impact in the pharma and drug discovery industry.

  3. AI for Deep Research Synthesis 0:58

    Gemini's research mode (Deep Research) assists with synthesizing ideas and connecting concepts, particularly useful for neuroscience research or academic papers.

Watch on YouTube Full article

Write Drunk, Edit Sober: Creating Generative Content Responsibly - Matthijs van der Veer thumbnail

· 56:54

Write Drunk, Edit Sober: Creating Generative Content Responsibly - Matthijs van der Veer

The talk addresses the proliferation of 'AI Slop'—low-quality, inauthentic content generated by LLMs—and provides a framework for developers to build automated systems that enforce quality. The core philosophy is shifting focus from merely generating content ('Write Drunk') to defining clear intent and implementing rigorous review processes ('Edit Sober'). Practical solutions involve using structured data inputs (like GitHub Issues) to capture user intent, applying Natural Language Processing (NLP) techniques like lemmatization for stylistic checks, and building automated quality gates that flag common LLM patterns (e.g., excessive emojis, M dashes, or generic corporate tropes).

Key takeaways

  1. Identify 'AI Slop' Patterns 0:23

    Common signs of low-quality AI content include overuse of emojis, the M dash (`—`), bold text, overly positive/generic language, and vague phrasing like 'In an era...' (0:023 - 0:045).

  2. Focus on Intent over Content 2:38

    The most critical step in generating quality AI content is defining the core intent: What do you want the audience to learn? Who should be here? And what can they accomplish? This structured approach guides the LLM (0:158 - 0:236).

  3. Automated Quality Gates are Essential 7:55

    Developers can build tools that enforce quality by implementing deterministic checks. Techniques include using NLP libraries like `spacy` for lemmatization to identify overused or non-standard vocabulary, and running pattern matching against known 'tropes' (0:475 - 1:239).

  4. Mitigate Automation Bias with Metrics 23:10

    To combat the tendency to overly trust machine output (automation bias), systems should provide explicit metrics, such as a confidence score or probability of error, rather than simply offering recommendations. Offering raw information is safer than recommending an action (1:390 - 2:150).

Watch on YouTube Full article

Stanford CS547 HCI Seminar | Spring 2026 | Show It or Tell It? Text, Visualization, and Combination thumbnail

· 56:19

Stanford CS547 HCI Seminar | Spring 2026 | Show It or Tell It? Text, Visualization, and Combination

This seminar explores the complex intersection of text and data visualization, arguing that language is a critical component of effective information design. The discussion moves from established cognitive theories (like Dual Coding Theory) to modern AI architectures, detailing how Multimodal Large Language Models (MLLMs) process combined visual and textual inputs using mechanisms like cross-attention. Key findings suggest that while the optimal balance between text and visuals is highly context-dependent, MLLMs are capable of deeply integrating both modalities.

Key takeaways

  1. Language is a key component of visualization 5:19

    Studies show that titles and labels receive long fixations during encoding and are the most likely elements to be recalled, suggesting language significantly impacts how data visualizations are understood. The speaker notes this was historically under-explored in the visualization community.

  2. Optimal design favors annotation over minimalism 21:30

    Research suggests that 'more text is better' for general information displays, provided the text is relevant and properly annotated. This finding challenges traditional minimalist principles in UI/UX design.

  3. MLLMs integrate modalities via cross-attention 41:20

    Multimodal LLMs (MLLMs) process text and visuals by transforming inputs into embeddings. The 'cross-modality embedding architecture' uses a cross-attention mechanism, allowing information to flow between the two distinct sequences (e.g., image tokens interacting with text tokens).

  4. Cognitive processing is context-dependent 30:00

    The speaker notes that understanding how humans integrate text and visuals is complex, citing conflicting evidence across theories (Dual Coding vs. Cognitive Load Theory). The choice of representation depends heavily on the specific task or cognitive ability.

Watch on YouTube Full article