Chiosa
Research collection

NLP & Language

Research on NLP & Language: explanations, evidence, limitations and connections between papers.

42 results

  1. Guided lessonNLP & Language

    Choose a past signal that fits the task and its resource limit

    A document can be compressed before anyone asks about it; a robot can learn a new task while still needing an old one. Reusing the past helps only if the retained signal supports the job ahead. Across four studies, the practical choice is where to place that signal and what it costs to keep or recreate. Their results favor task-relevant signals in their tested settings, while the studies measure different outcomes and resources.

  2. Guided lessonNLP & Language

    Instruction changes can steer behavior or expose wording sensitivity

    A changed instruction can help a system complete a task, or it can reveal that a decision depends on wording. A robot’s request, a stalled math solution, and a guard reviewing a tool call make those purposes easy to confuse. The studies offer a bounded way to separate them: test steering by the task outcome it seeks to improve, and test sensitivity by changing one input feature while keeping the case fixed. The result belongs to the model, task, and comparison that produced it.

  3. Guided lessonNLP & Language

    Read the evaluation protocol before trusting a benchmark score

    Imagine seeing different accuracy scores for the same video model on the same benchmark. The model weights may be unchanged, yet the evaluator can choose different frames, process them differently, or score the response by a different rule. Across video questions, Taiwan knowledge questions, and dependency repairs, these studies show why a result needs its protocol beside it. A compact test can make a comparison less costly in its tested setting, while its task coverage still limits the claim. For a repair, success also depends on which checks the verifier runs.

  4. Guided lessonNLP & Language

    Check what stays useful before reusing computation

    A recommendation feature can outlive its usefulness, a matrix update can arrive with a new set of changed inputs, and a robot can see a scene that has just moved. Keeping prior work may save computation, but its value depends on what was kept and what changed. Across these studies, the useful first step is to identify the reusable work and its conditions, then measure the outcome that matters for that system. Removing a feature may raise serving throughput; retaining a matrix schedule may lose to a simpler update; refreshing fewer robot features may shorten an action request. Those are distinct findings in distinct settings.