How Small Model Evaluation Prompts Can Mislead and How to Fix Them

A detailed analysis on r/LocalLLaMA explains why evaluation prompts for small models (like 7B or 12B parameter models) often produce misleading, overly optimistic scores that don't match actual output quality. The core issue isn't model capability but how prompts activate different cognitive pathways in transformer architectures.
The Three Cognitive Modes of Transformers
The post identifies three functional pathways that models use based on prompt language:
- Dimension 1 (D1) — Factual Recall: Activated by questions like "What is...", "Define...", "When did...". The model retrieves knowledge stored during training. For evaluation tasks, this is mostly irrelevant.
- Dimension 2 (D2) — Application and Instruction Following: Activated by language like "Analyze...", "Classify...", "Apply these criteria...". The model applies explicit rules, follows structured instructions, and classifies inputs against provided criteria. This is the reliable pathway where small models are genuinely competent.
- Dimension 3 (D3) — Emotional and Empathic Inference: Activated by language like "How should this feel?", "What emotional response is appropriate?", "As an empathetic assistant...". The model infers unstated emotional context and makes normative judgments about how things "should" feel, routing through RLHF conditioning rather than evidence in the prompt. Small models are unreliable here, with bias consistently running positive and supportive regardless of actual content.
The Routing Insight
The key insight: "Analyze the emotional content" activates D2 (the model looks at text and classifies it), while "What should the user be feeling?" activates D3 (the model guesses what a helpful AI would say). These feel like equivalent questions but produce systematically different outputs.
Concrete Failure Example
The author tested this empirically with a Mistral 7B sentiment analyzer for a conversational AI system. The original prompt (simplified):
You are an empathetic AI companion analyzing emotional content. Analyze this message and return: { "tone": "warm, affectionate, grateful", "intensity": 0.0 to 1.0, "descriptors": ["example1", "example2"] }
What happened: Neutral messages returned slightly positive tone. Mildly negative messages scored as neutral or lightly positive. Intensity values for negative content were consistently lower than intensity values for equivalent positive content. This systematic, reproducible bias is called positive phantom drift — the model's RLHF conditioning pulling outputs toward supportive, positive responses regardless of actual input content.
Three things caused this failure:
- "Empathetic AI companion" activated D3, shifting the model into the social-expectation pathway
- Example values in the JSON template ("warm, affectionate, grateful") primed the model toward positive outputs
- The model was generating what a helpful AI would say rather than analyzing the evidence
The post emphasizes that small models can perform well on evaluation tasks when prompts deliberately activate D2 (application/instruction following) rather than D3 (emotional inference). The difference between "Analyze the emotional content" and "What should the user be feeling?" determines whether you get reliable classification or biased social expectation responses.
📖 Read the full source: r/LocalLLaMA
👀 See Also

Opus 4.7 Broke 40% of Prompts; Fix Was Structuring CLAUDE.md and Skills
After Opus 4.7 degraded ~40% of prompts across 6 setups, a fractional head of AI fixed it by replacing ad-hoc prompts with structured Skill files, hierarchical CLAUDE.md, and separate memory files — reducing token usage 22% and iteration turns from 3-4 to 1-2.

OpenClaw Fallback Chains Preserve Uptime but Can Quietly Lower Reliability
OpenClaw's model fallback mechanism can mask reliability issues. A smaller fallback model may pass simple tasks but fail complex ones, costing more in retries and review.

Using AI as a Cognitive Partner Instead of a Code Factory
A Reddit post proposes a system prompt called 'Cognitive Authorship Copilot' that forces AI to act as a pair programming partner rather than an autonomous solution generator, with three intervention levels based on task complexity.

vLLM Setup and Testing on 10x NVIDIA V100 Server with 320GB VRAM
A lawyer building a local AI server for legal work shares vLLM testing results on 10x Tesla V100 SXM2 32GB GPUs, detailing what works (FP16 unquantized, bitsandbytes 4-bit) and what doesn't (GPTQ, AWQ, FlashAttention2) on Volta architecture.