This prompt is for verification teams, editorial QA engineers, and AI pipeline builders who need to assess whether an attributed quote or paraphrase preserves the original speaker's communicative intent. Literal accuracy is necessary but insufficient. A quote can be word-perfect yet still distort meaning through selective extraction, tone erasure, or context removal. This prompt produces an intent-alignment score with evidence from surrounding source context, enabling automated triage before human review.
Prompt
Speaker Intent Preservation Evaluation Prompt

When to Use This Prompt
A guide for deploying the Speaker Intent Preservation Evaluation Prompt to distinguish between literal accuracy and genuine meaning preservation in attributed quotes.
Use this when your verification workflow must distinguish between 'the words are correct' and 'the meaning is preserved.' It is designed to sit downstream from a Quote-to-Source Comparison Prompt, which handles string-level fidelity. Once a quote passes a literal match, this prompt evaluates whether the use of that quote is faithful to the speaker's position. The output is a structured score and rationale that can be used to route borderline cases to human reviewers, auto-approve high-confidence matches, or flag content for revision. The harness should include a threshold for automatic escalation: for example, any intent-alignment score below 0.8 triggers a human review task with the full evidence package.
Do not use this prompt for simple string-matching or binary misquotation detection. That work belongs to the Quote-to-Source Comparison Prompt Template or Misquotation Detection Prompt in this pillar. This prompt is also not a replacement for a full editorial review; it is a triage and acceleration tool. In high-stakes domains like legal or medical reporting, a human must always review the final determination, regardless of the model's confidence score.
Use Case Fit
Where the Speaker Intent Preservation Evaluation Prompt delivers reliable results and where it introduces risk. Use these cards to decide if this prompt fits your verification workflow before integrating it into a production pipeline.
Good Fit: Editorial Quote Review
Use when: An editor needs to verify that a paraphrased or quoted statement in a draft article preserves what the original speaker actually meant, not just the literal words. Guardrail: Pair this prompt with the Quote-to-Source Comparison Prompt for a complete fidelity check that covers both wording and intent.
Bad Fit: Real-Time Chat Moderation
Avoid when: Latency budgets are under 500ms or the model must make accept/reject decisions without human review. Intent analysis requires surrounding context and careful reasoning that is too slow and nuanced for real-time filtering. Guardrail: Use a lightweight classification router for real-time decisions and reserve this prompt for asynchronous editorial review.
Required Input: Full Source Context
Risk: Evaluating speaker intent from an isolated quote without the surrounding paragraphs, speaker history, or communicative situation produces unreliable intent scores. Guardrail: Require at least 200 words of surrounding source context and the full attributed statement as mandatory inputs. Reject evaluations when context is truncated.
Operational Risk: Over-Confidence on Ambiguous Intent
Risk: The model may assign high intent-alignment scores to statements where the original speaker's intent was genuinely ambiguous, creating false assurance. Guardrail: Require the output schema to include an ambiguity_flag field. Route any result with ambiguity_flag: true to human review regardless of the numeric score.
Operational Risk: Cultural and Linguistic Nuance Loss
Risk: Speaker intent often relies on cultural context, irony, understatement, or domain-specific conventions that the model may not recognize, especially across languages. Guardrail: Add a cultural_context_note field to the output schema. Flag outputs where the source material contains culture-specific communication patterns and route to a reviewer with domain or regional expertise.
Bad Fit: Legal Deposition Analysis Without Review
Avoid when: The output will be used in legal proceedings, depositions, or compliance filings without attorney review. Intent interpretation is a legal argument, not a verifiable fact. Guardrail: This prompt may assist legal teams in preparing analysis but must never be the final arbiter. All outputs in legal contexts require explicit human attorney review and should be labeled as AI-assisted analysis, not determination.
Copy-Ready Prompt Template
A reusable system prompt for evaluating whether a quote or paraphrase preserves the original speaker's communicative intent.
This prompt template is the core instruction set for the Speaker Intent Preservation Evaluation workflow. It is designed to be copied directly into your system prompt or a dedicated user message in your verification pipeline. The template uses square-bracket placeholders for all dynamic inputs, allowing you to wire it into an application that supplies the original source material, the attributed statement, and your specific evaluation constraints. Before using this prompt, ensure you have the full surrounding context of the original statement, not just the isolated sentence, as intent cannot be reliably assessed without it.
textYou are an expert in linguistic forensics and editorial verification. Your task is to evaluate whether an attributed quote or paraphrase preserves the original speaker's communicative intent, not just the literal wording. Intent includes the speaker's primary assertion, the action they are performing (e.g., stating a fact, making a prediction, issuing a warning, expressing doubt), and the degree of certainty they conveyed. You will receive the following inputs: - [ORIGINAL_SOURCE_TEXT]: The full, unedited passage from the original speaker, including several sentences of surrounding context. - [ATTRIBUTED_STATEMENT]: The quote or paraphrase as it appears in the content being verified. - [SPEAKER_IDENTITY]: The name and role of the original speaker. - [CONTENT_DOMAIN]: The subject area (e.g., finance, medicine, politics) to calibrate your understanding of domain-specific language. Follow these steps: 1. Identify the core communicative intent of the [ORIGINAL_SOURCE_TEXT]. What is the speaker's main point, what speech act are they performing, and what is their expressed level of certainty? 2. Identify the core communicative intent of the [ATTRIBUTED_STATEMENT] in isolation. 3. Compare the two intents. Determine if the attributed statement preserves, distorts, reverses, or overstates the original intent. 4. Assign an intent-alignment score on a 1-5 scale: - 5: Intent perfectly preserved. - 4: Minor nuance lost, but core intent intact. - 3: Intent is partially preserved but a significant qualifier or aspect is missing or altered. - 2: Intent is substantially distorted; a reasonable reader would take away a different meaning. - 1: Intent is completely reversed or fabricated. 5. Provide a concise, evidence-grounded rationale for your score, quoting the specific phrases from both texts that support your judgment. Output your findings in a single, valid JSON object conforming to this schema: { "original_intent_summary": "string", "attributed_intent_summary": "string", "intent_alignment_score": integer (1-5), "rationale": "string with quoted evidence", "distortion_flags": ["string"] } [CONSTRAINTS]: - Do not evaluate the truthfulness of the original statement. Only evaluate the fidelity of the attribution. - If the [ORIGINAL_SOURCE_TEXT] is insufficient to determine intent, set the score to null and explain why in the rationale. - If the [ATTRIBUTED_STATEMENT] is a fabrication with no basis in the source, set the score to 1 and flag it as "fabrication". - The "distortion_flags" array should use controlled vocabulary: "overstatement", "understatement", "certainty_shift", "context_stripping", "cherry_picking", "fabrication", "false_equivalence", "none".
To adapt this template for your application, replace the square-bracket placeholders with your actual data. The [ORIGINAL_SOURCE_TEXT] must include enough surrounding context—typically 2-3 sentences before and after the quoted segment—to ground the intent analysis. The [CONSTRAINTS] section is critical for high-risk domains; you should add domain-specific rules here, such as requiring a higher bar for certainty in medical or legal contexts. After generating the output, always validate the JSON schema before passing the result downstream. For production use, pair this prompt with a retry mechanism that feeds schema validation errors back to the model for self-correction, and route any output with a score of 2 or 1 directly to a human review queue.
Prompt Variables
Inputs the Speaker Intent Preservation Evaluation Prompt needs to work reliably. Validate these before sending to the model.
| Placeholder | Purpose | Example | Validation Notes |
|---|---|---|---|
[QUOTE_OR_PARAPHRASE] | The attributed statement to evaluate for intent preservation | The CEO said the company is exploring strategic alternatives. | Must be a non-empty string. Check for length > 10 characters. Flag if the text appears to be a full paragraph rather than a discrete attributed statement. |
[ORIGINAL_SOURCE_TEXT] | The verbatim source material from which the quote or paraphrase was derived | We are considering all options to maximize shareholder value, including a potential sale or merger. | Must be a non-empty string. Validate that the source text is at least as long as the quote. Reject if the source text is identical to the quote with no surrounding context. |
[SURROUNDING_CONTEXT] | Additional sentences before and after the original statement in the source to capture communicative intent | When asked about market rumors, the CEO stated: 'We are considering all options...' The board has not made a final decision. | Can be null if unavailable. If provided, must contain the [ORIGINAL_SOURCE_TEXT] as a substring. Warn if context is under 50 characters. |
[SPEAKER_ROLE] | The role or title of the person being quoted, used to calibrate intent interpretation | Chief Executive Officer during Q4 2024 earnings call | Must be a non-empty string. Validate against a known taxonomy of roles if available. Flag if role is 'unknown' or 'anonymous' as this reduces intent evaluation reliability. |
[COMMUNICATION_MEDIUM] | The format in which the original statement was made, affecting intent-carrying signals | Earnings call transcript, written press release, social media post, or interview | Must be one of a predefined enum: transcript, press_release, social_media, interview, speech, email, or other. Reject unrecognized values. Medium affects how hedging, tone, and audience design are interpreted. |
[DOMAIN] | The subject domain for calibrating domain-specific intent norms | Corporate finance, clinical medicine, legal testimony, or political speech | Must be a non-empty string. Validate against a supported domain list. If unsupported domain is provided, route to a generalist evaluation path with a warning flag. |
[PREVIOUS_VERIFICATION_RESULTS] | Optional prior verification outputs for this quote to avoid redundant re-evaluation | JSON object with fidelity_score, discrepancy_flags, and reviewer_notes from a prior Quote-to-Source Comparison run | Can be null. If provided, must conform to the Quote-to-Source Comparison output schema. Use to skip re-evaluation of already-verified literal accuracy before assessing intent. |
Implementation Harness Notes
How to wire the Speaker Intent Preservation Evaluation Prompt into a production verification pipeline with validation, routing, and human review.
This prompt is not a standalone tool; it is a scoring component inside a larger quote-verification pipeline. The harness must enforce a strict output contract, validate the JSON schema, and route results based on the intent_alignment_score. A score below a defined threshold (e.g., 0.7) should automatically escalate to a human review queue, while scores above the threshold can proceed to automated publication or further downstream checks. The harness should never treat a missing or malformed score as a passing grade.
Implement the harness with a retry-and-validate pattern. First, parse the model's JSON output and validate it against the expected schema: intent_alignment_score (float 0-1), rationale (string), semantic_drift_flags (list of strings), and recommendation (enum: accept, revise, escalate). If validation fails, retry the prompt once with the validation error message appended to the [CONSTRAINTS]. If the retry also fails, log the raw output and route the item to a human review_failed_parse queue. For high-stakes content, consider using a second, cheaper model as a judge to verify the primary model's score; a discrepancy greater than 0.2 between the two models should also trigger escalation.
Log every evaluation as a structured event: the original quote, the source context, the model's score, the rationale, and the final routing decision. This audit trail is critical for calibrating the intent_alignment_score threshold over time. Avoid wiring this prompt directly to a publish action without a human-in-the-loop circuit breaker for low-confidence or high-risk content. The next step is to integrate this harness with your existing content management system (CMS) or verification queue, ensuring that the escalate recommendation creates a task pre-populated with the quote, source, and the model's specific concerns.
Expected Output Contract
Strict JSON schema for the Speaker Intent Preservation Evaluation output. Use this contract to validate model responses before routing to downstream systems or human review queues.
| Field or Element | Type or Format | Required | Validation Rule |
|---|---|---|---|
intent_alignment_score | number (0.0-1.0) | Must be a float between 0.0 and 1.0 inclusive. Reject if out of range or non-numeric. | |
intent_preservation_category | string (enum) | Must match one of: 'fully_preserved', 'substantially_preserved', 'partially_distorted', 'significantly_distorted', 'inverted'. Reject on unknown values. | |
speaker_communicative_intent | string | Must be a non-empty string summarizing the original speaker's intent derived from [SOURCE_CONTEXT]. Reject if empty or identical to the quoted text. | |
distortion_flags | array of strings | Each element must be a non-empty string from the allowed flag list: 'context_stripping', 'cherry_picking', 'tone_shift', 'emphasis_change', 'qualification_removal', 'temporal_misplacement', 'none'. Reject if array contains unknown flags. | |
missing_context_excerpts | array of objects | If present, each object must contain 'excerpt' (string) and 'relevance' (string enum: 'critical', 'supporting', 'tangential'). Null allowed when no context is missing. | |
semantic_drift_description | string or null | If intent_preservation_category is 'partially_distorted' or worse, this must be a non-empty string explaining the drift. Otherwise null is valid. | |
confidence_level | string (enum) | Must be one of: 'high', 'medium', 'low'. Reject on unknown values. 'low' confidence must route to human review regardless of score. | |
requires_human_review | boolean | Must be true if confidence_level is 'low' or intent_preservation_category is 'significantly_distorted' or 'inverted'. Validate against these conditions post-parse. |
Common Failure Modes
Speaker intent preservation fails in predictable ways. These cards cover the most common failure modes when evaluating whether a quote or paraphrase preserves original communicative intent, with concrete guardrails for each.
Literal Match, Intent Mismatch
What to watch: The prompt confirms word-level accuracy but misses that the speaker's intended meaning was ironic, conditional, or hypothetical. Verbatim text match produces a false sense of fidelity. Guardrail: Require the prompt to extract and compare the speaker's communicative goal—not just the words—by analyzing surrounding context, tone markers, and hedging language before scoring alignment.
Context Window Truncation
What to watch: The surrounding source context that disambiguates intent is cut off by token limits, causing the prompt to evaluate intent from an incomplete picture. This is especially dangerous with long interviews or speeches. Guardrail: Implement a context-expansion step that retrieves at least [N] sentences before and after the quoted passage before running intent evaluation. Flag results where context boundaries were hit.
Cultural and Domain Pragmatics Blindness
What to watch: The prompt interprets the speaker's words through a generic lens and misses domain-specific conventions, politeness strategies, or cultural indirectness that carry the real intent. A diplomatic "we'll consider it" may mean rejection. Guardrail: Include domain and cultural context metadata in the prompt input. For high-stakes evaluations, route to human reviewers with domain expertise when the prompt's confidence falls below threshold.
Overweighting Surface Sentiment
What to watch: The prompt conflates sentiment polarity with intent. A speaker can express negative sentiment while intending to motivate improvement, or positive sentiment while intending to dismiss. Sentiment alignment is not intent alignment. Guardrail: Add an explicit instruction to separate sentiment analysis from intent classification. Require the output to label sentiment and intent independently, with evidence for each, before computing the final alignment score.
False Alignment from Vague Scoring
What to watch: The prompt produces a middling intent-alignment score with generic rationale that passes automated checks but provides no actionable signal. "Mostly aligned" hides real distortion. Guardrail: Require the output schema to include specific distortion categories (e.g., omission, emphasis shift, modal weakening) with evidence excerpts. Set a minimum specificity threshold—if no distortion category is identified, the score must be justified with concrete comparisons.
Paraphrase Drift Accumulation
What to watch: Each paraphrase revision introduces small semantic shifts that individually pass intent checks but cumulatively invert the original meaning across multiple edits. Single-step evaluation misses this. Guardrail: For document revision workflows, compare the final paraphrase directly against the original source, not just the previous version. Implement a cumulative drift alert that triggers when semantic distance from the original exceeds a defined threshold across revisions.
Evaluation Rubric
Run these checks against a golden dataset of 50+ human-annotated examples to evaluate intent preservation output quality before shipping.
| Criterion | Pass Standard | Failure Signal | Test Method |
|---|---|---|---|
Intent Alignment Score Calibration | Model score within ±0.15 of human-annotated ground truth for 90% of examples | Systematic overconfidence (score >0.9 when human score <0.6) or underconfidence (score <0.4 when human score >0.8) | Pearson correlation ≥0.85 between model scores and human scores across golden set |
Evidence Grounding Completeness | Every intent-alignment score cites at least one specific source passage supporting the assessment | Score provided without source citation or citation references passage unrelated to intent claim | Parse output for non-empty [EVIDENCE] field; verify citation exists in provided source material via substring match |
Context-Aware Intent Detection | Assessment references surrounding source context beyond the quoted span when context is provided in [SURROUNDING_CONTEXT] | Assessment treats quote in isolation despite available surrounding context that would change intent interpretation | Spot-check 20 examples where surrounding context is known to alter intent; verify model output references that context |
Distortion Category Accuracy | Distortion category label matches human annotation for ≥85% of examples in golden set | Model labels meaning-preserving paraphrase as distortion or labels clear distortion as acceptable | Confusion matrix comparison between model-assigned [DISTORTION_CATEGORY] and human labels; target F1 ≥0.85 per category |
False Positive Control on Benign Paraphrases | ≤5% false positive rate on golden examples annotated as intent-preserving | Model flags routine rephrasing, synonym substitution, or grammatical restructuring as intent distortion | Run against 30+ known-intent-preserving paraphrase pairs; count false positives; reject if >5% |
False Negative Detection on Meaning Reversals | ≥95% recall on golden examples annotated as intent-distorting | Model passes a paraphrase that reverses the speaker's position, removes negation, or swaps subject and object roles | Run against 30+ known-intent-distorting pairs; count missed detections; reject if recall <95% |
Schema Compliance and Field Completeness | 100% of outputs parse as valid JSON matching [OUTPUT_SCHEMA] with all required fields present and non-null where applicable | Missing [INTENT_ALIGNMENT_SCORE], null [RATIONALE], or extra fields not in schema | Automated JSON Schema validation against expected schema; reject run if any output fails parse or required-field check |
Abstention on Insufficient Context | Model abstains (confidence null or abstention flag true) when [SURROUNDING_CONTEXT] is empty and quote alone is ambiguous for intent assessment | Model assigns high-confidence intent score to ambiguous quote without acknowledging insufficient context | Curate 10 examples with deliberately insufficient context; verify model outputs abstention signal or confidence below threshold |
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Adapt This Prompt
How to adapt
Use the base prompt with a simplified output schema. Focus on getting the intent-alignment score and a single-sentence rationale. Skip the structured evidence extraction and just ask for a 1-5 score with a brief explanation.
codeEvaluate whether the [QUOTE_OR_PARAPHRASE] preserves the original speaker's communicative intent from [SOURCE_CONTEXT]. Return a score from 1 (completely distorted) to 5 (fully preserved) with a one-sentence rationale.
Watch for
- Scores that don't match the rationale text
- Over-reliance on literal wording match instead of intent
- No distinction between minor nuance loss and meaning reversal

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us