This prompt is built for editorial teams, fact-checkers, and verification engineers who need to confirm that a quote attributed to a specific person in a published article, transcript, or social post actually matches what that person said in the original source material. The core job-to-be-done is not just string matching—it's verifying fidelity of meaning when the original source is audio or video, the quoted form is text, and the attribution chain crosses formats. You should use this prompt when you have a claimed quote, a candidate source recording or transcript, and you need a structured verdict on whether the attribution is accurate, paraphrased, context-stripped, or fabricated.
Prompt
Multimodal Quote Attribution Verification Prompt

When to Use This Prompt
Define the job, reader, and constraints for verifying quote attribution across text, audio, and video sources.
The ideal user is someone integrating this into a content verification pipeline: a newsroom tools engineer, a platform trust-and-safety developer, or an AI architect building a claims-verification harness. Required context includes the full attributed quote as it appears in the published content, the speaker's name as attributed, and the source evidence—ideally a timestamped transcript segment, an audio clip, or a video segment with speaker identification. The prompt is designed to work even when the evidence format differs from the quote format, but it assumes you have already performed speaker diarization or identity labeling on the source media. Do not use this prompt for general sentiment analysis, for verifying statistical claims, or for checking whether a quote is factually true—only whether it was said by the attributed person in a way that preserves the original meaning.
This prompt is not a replacement for human editorial judgment in high-stakes publishing decisions. It produces a structured fidelity assessment with flags for paraphrasing, context-stripping, and speaker mismatch, but the final decision to publish, correct, or retract a quote should involve human review. The prompt is also not designed for real-time live-stream verification, for quotes translated across languages without back-translation evidence, or for situations where the original source is unavailable and you are relying on second-hand accounts. In those cases, the prompt should abstain and flag the evidence gap rather than guess. Wire this prompt into a pipeline that includes upstream speaker diarization, downstream human review routing for low-confidence matches, and logging for audit trails.
Use Case Fit
Where the Multimodal Quote Attribution Verification Prompt works, where it fails, and the operational prerequisites for production use.
Good Fit: Editorial Quote Auditing
Use when: editorial teams need to verify that published quotes match original audio, video, or text sources before publication. Guardrail: require side-by-side source-to-quote alignment output with fidelity scores, not a binary pass/fail.
Bad Fit: Real-Time Live Transcription
Avoid when: latency requirements are sub-second and the model must verify attribution during live captioning. Guardrail: use this prompt for post-hoc batch auditing only; pair with a streaming ASR pipeline for live use cases.
Required Inputs: Source-Quote Pairs with Format Metadata
What to watch: the prompt fails silently when given only the quote without the original source material. Guardrail: enforce a strict input schema requiring [QUOTE_TEXT], [SOURCE_TEXT_OR_TRANSCRIPT], [SOURCE_FORMAT], and [SPEAKER_ID] before invocation.
Operational Risk: Paraphrase vs. Fabrication Confusion
What to watch: the model may flag legitimate paraphrasing as misattribution or, conversely, accept fabricated quotes that are semantically similar. Guardrail: implement a human-review threshold for fidelity scores in the 0.4–0.7 range and log all borderline cases for audit.
Operational Risk: Cross-Format Speaker Disambiguation
What to watch: when the same speaker appears in text, audio, and video sources, the model may conflate identities or miss attribution shifts. Guardrail: supply explicit [SPEAKER_ID] tags per source segment and test with known speaker-confusion edge cases in eval.
Operational Risk: Context-Stripping False Positives
What to watch: the model may flag a quote as context-stripped when surrounding context is present but formatted differently across modalities. Guardrail: include [CONTEXT_WINDOW] fields in the input and calibrate context-stripping flags against human-annotated examples.
Copy-Ready Prompt Template
A reusable prompt template for verifying quote attribution and fidelity across text, audio, and video sources.
This prompt template is designed to be the core instruction set for a multimodal quote attribution verification system. It accepts a target quote, the attributed speaker, the source context where the quote appears, and the original reference material. The model is instructed to produce a structured verification output, including a fidelity score, speaker identity notes, and flags for context-stripping or paraphrasing. The square-bracket placeholders allow you to inject dynamic content from your application's retrieval or user-input layer before each inference call.
textYou are a meticulous editorial fact-checker specializing in quote attribution and fidelity across text, audio, and video sources. Your task is to verify the accuracy and attribution of a target quote against provided original source material. The target quote and its context may come from one format (e.g., a written article, an audio transcript, a video description), while the original evidence may be in another. You must account for these format differences. ## INPUT **Target Quote:** [TARGET_QUOTE] **Attributed Speaker:** [ATTRIBUTED_SPEAKER] **Source Context (where the target quote appears):** [SOURCE_CONTEXT] **Original Reference Material (ground truth):** [ORIGINAL_REFERENCE] ## CONSTRAINTS - Do not assume the target quote is accurate. Your job is to verify it. - Distinguish between verbatim matches, defensible paraphrases, and meaning distortions. - If the original reference is audio or video, consider transcription errors, tone, and non-verbal cues described in the reference. - If speaker identity is ambiguous in the original reference, flag it rather than guessing. - If the target quote strips critical context that changes its meaning, you must flag it as a context-stripping violation. ## OUTPUT_SCHEMA Respond with a single JSON object conforming to this schema: { "quote_fidelity_score": "EXACT_MATCH | FAITHFUL_PARAPHRASE | LOOSE_PARAPHRASE | MINOR_DISTORTION | MAJOR_DISTORTION | FABRICATED", "speaker_identity_verification": "CONFIRMED | PROBABLE | AMBIGUOUS | MISATTRIBUTED | UNVERIFIABLE", "context_stripping_flag": true or false, "context_stripping_explanation": "string, required if flag is true", "evidence_citation": "A direct quote or timestamp from the [ORIGINAL_REFERENCE] that supports your assessment", "verification_rationale": "A concise explanation of your comparison, noting any format-specific challenges (e.g., OCR errors, transcription ambiguity)", "requires_human_review": true or false }
To adapt this template, replace the placeholders with data from your application. For example, [TARGET_QUOTE] might be a user-submitted string, while [ORIGINAL_REFERENCE] could be a text chunk retrieved via RAG or a transcript from an audio file. The OUTPUT_SCHEMA is designed to be machine-readable, allowing your harness to parse the JSON and route the result. If the requires_human_review field is true or the quote_fidelity_score is MAJOR_DISTORTION or FABRICATED, your implementation should automatically escalate to a human review queue. Before deploying, test this prompt with edge cases like overlapping speech in transcripts, OCR errors in image-based quotes, and paraphrases that change numerical values.
Prompt Variables
Required inputs for the Multimodal Quote Attribution Verification Prompt. Each variable must be populated before the prompt is assembled and sent. Validation notes describe checks to apply in the harness before execution.
| Placeholder | Purpose | Example | Validation Notes |
|---|---|---|---|
[QUOTE_TEXT] | The attributed quote string being verified | "We are seeing unprecedented demand," said CEO Jane Smith during the Q3 earnings call. | Non-empty string; max 2000 chars; must be the exact quote as published, not a paraphrase |
[ATTRIBUTED_SPEAKER] | The person or entity to whom the quote is attributed | Jane Smith, CEO | Non-empty string; should match a known entity in the source metadata; fuzzy-match against speaker list if available |
[SOURCE_CONTENT] | The original source material where the quote allegedly appears | Full transcript of Q3 2024 earnings call, or audio file URI, or video segment with timestamps | Non-empty; format must be declared via [SOURCE_FORMAT]; if audio/video, pre-processed transcript should be provided alongside media reference |
[SOURCE_FORMAT] | The modality of the source content | text/transcript, audio/mp3, video/mp4, image/screenshot | Must be one of the allowed format enum values; determines which comparison sub-prompt variant is selected |
[PUBLICATION_CONTEXT] | The surrounding text or metadata from where the quote was published | News article paragraph containing the quote, plus article title, date, and outlet name | Non-empty string; include at least 2 sentences before and after the quote; null allowed only if quote is standalone with no surrounding context |
[SPEAKER_IDENTITY_EVIDENCE] | Evidence confirming the speaker's identity in the source | Speaker diarization labels from audio processing, on-screen name caption from video, byline from transcript | Nullable if identity is assumed; required for high-confidence attribution; if null, prompt must flag identity as unverified |
[PARAPHRASE_TOLERANCE] | Threshold for accepting paraphrased quotes as matches | strict, moderate, lenient | Must be one of the enum values; strict requires near-verbatim match; lenient allows semantic equivalence; moderate balances both |
[OUTPUT_SCHEMA] | Expected structure for the verification result | JSON schema with fields: quote_fidelity_score, speaker_identity_verified, context_stripping_flag, evidence_snippets, confidence | Must be a valid JSON Schema object; harness should validate output against this schema post-generation |
Implementation Harness Notes
How to wire the Multimodal Quote Attribution Verification Prompt into a production application with validation, retries, and human review.
This prompt is designed to be a single step within a larger verification pipeline. It expects a structured input containing the attributed quote, the speaker identity, the source medium, and the reference evidence. The application layer is responsible for assembling this input from upstream extraction systems—such as an ASR pipeline for audio, an OCR module for screenshots, or a direct text parser for written articles. Do not pass raw, unprocessed files to this prompt; the model needs pre-extracted, text-based claims and evidence to perform reliable comparison.
The output is a structured JSON object with quote-fidelity scores, speaker-identity verification notes, and context-stripping flags. Implement a strict post-processing validator that checks for the presence of all required fields, enforces the score range (e.g., 0.0 to 1.0), and confirms that flag fields are boolean. If validation fails, use a retry loop with a maximum of two attempts, appending the specific validation error to the prompt context on retry. For cross-format speaker disambiguation, the harness should pre-process evidence to include a speaker_label field derived from diarization metadata or document bylines, which the prompt uses to match against the claimed speaker.
Given the high-risk nature of misattribution in editorial and compliance contexts, this workflow requires a human review step for any output where the fidelity_score falls below 0.85 or the context_stripping_flag is true. The application should route these low-confidence results to a review queue, presenting the original quote, the evidence snippet, and the model's structured notes side-by-side. Log every verification attempt, including the full prompt, raw model output, validation result, and final routed decision, to create an audit trail. Avoid using this prompt for real-time, low-latency applications; the model's reasoning over nuanced paraphrasing and speaker identity is better suited for asynchronous batch processing where accuracy is prioritized over speed.
Expected Output Contract
Fields, format, and validation rules for the structured output of the Multimodal Quote Attribution Verification Prompt. Use this contract to parse and validate the model's response before downstream consumption.
| Field or Element | Type or Format | Required | Validation Rule |
|---|---|---|---|
quote_fidelity_score | number (0.0-1.0) | Must be a float between 0 and 1. Null allowed only if quote is unverifiable. Check: parse as float, enforce range. | |
speaker_identity_match | boolean | Must be true or false. Check: strict boolean parse. If speaker cannot be disambiguated, set to false and populate speaker_identity_notes. | |
speaker_identity_notes | string | Required if speaker_identity_match is false. Must contain a non-empty explanation of the ambiguity. Check: non-empty string when match is false. | |
context_stripping_flag | boolean | Must be true if the attributed quote omits or alters surrounding context in a way that changes meaning. Check: strict boolean parse. | |
context_stripping_detail | string | Required if context_stripping_flag is true. Must describe the missing or altered context. Check: non-empty string when flag is true. | |
source_evidence_reference | object | Must contain source_type (enum: text, audio, video, transcript) and source_location (string). Check: validate enum membership and non-empty location. | |
paraphrase_classification | enum | Must be one of: verbatim, minor_paraphrase, substantial_paraphrase, misrepresentation. Check: strict enum validation. | |
cross_format_disambiguation_notes | string | Required when evidence and claim originate from different formats. Must explain how speaker identity was resolved across formats. Check: non-empty string when source formats differ. |
Common Failure Modes
What breaks first when verifying quotes across text, audio, and video, and how to guard against it.
Speaker Identity Disambiguation
What to watch: The model attributes a quote to the wrong speaker when multiple people have similar voices, titles, or speaking patterns, or when speaker labels in a transcript are ambiguous. This is especially common in panel discussions, interviews with multiple participants, and audio with overlapping speech. Guardrail: Provide a speaker manifest with unique identifiers, role descriptions, and sample quotes for each speaker. Require the model to output a speaker-identity confidence score per quote and flag any attribution below a threshold for human review.
Paraphrase Drift and Meaning Distortion
What to watch: The model accepts a paraphrased quote as matching the original when the paraphrase changes the meaning, softens a controversial statement, or omits critical qualifiers. This is common when the paraphrase uses synonyms that shift connotation or when conditional statements are rendered as absolute claims. Guardrail: Require the model to extract and compare the core proposition, modal verbs, and hedging language separately from surface-level lexical similarity. Add a dedicated 'meaning-preservation' check that flags any dropped qualifiers, tense shifts, or scope changes.
Context-Stripping and Quote Fragmentation
What to watch: A quote is verified as accurate in isolation but loses its original meaning because surrounding context, preceding questions, or follow-up clarifications are stripped away. This is the most common source of quote-based misinformation in production. Guardrail: Require the model to retrieve and include the surrounding context window—at minimum the preceding and following two sentences or 30 seconds of audio—and flag any quote where the meaning shifts when that context is included. Output a 'context-stripping risk score' for every verified quote.
Transcription Error Cascades
What to watch: The model verifies a quote against an inaccurate transcript, so the verification itself is built on a faulty foundation. Common transcription errors include homophone confusion, missing negations, and dropped words in fast speech. These errors propagate into false-positive matches or false-negative mismatches. Guardrail: Require word-level transcription confidence scores from the ASR system as an input. Flag any quote where the transcript words involved in the match fall below a confidence threshold. For high-stakes verification, route low-confidence transcript segments to human transcription review before quote comparison.
Cross-Format Temporal Misalignment
What to watch: A quote attributed to a specific timestamp in audio or video is verified against a text source from a different time, or the model matches a quote to the wrong segment of a long recording. This produces false matches when similar statements appear at multiple points. Guardrail: Require the model to output precise timecodes or byte-offsets for both the quoted claim and the source evidence. Implement a temporal proximity check—if the model matches a quote to a source segment more than N seconds away from the expected timestamp, flag for review. Use speaker-turn boundaries as additional alignment anchors.
Format-Biased Confidence Scoring
What to watch: The model assigns higher confidence to text-to-text quote matches than to audio-to-text or video-to-text matches, even when the evidence quality is equivalent, because it is more comfortable with text-native comparisons. This skews verification results and can cause the system to over-rely on text transcripts while ignoring direct audio evidence. Guardrail: Calibrate confidence scores per format pair using a held-out evaluation set with human-annotated ground truth. Apply a format-pair adjustment factor to raw confidence scores. Log the format pair for every verification result so operators can monitor for format bias in production dashboards.
Evaluation Rubric
Use this rubric to test the Multimodal Quote Attribution Verification Prompt before deployment. Each criterion targets a known failure mode in cross-format quote verification. Run these tests against a golden dataset of 20-30 quote-evidence pairs spanning text, audio transcripts, and video captions.
| Criterion | Pass Standard | Failure Signal | Test Method |
|---|---|---|---|
Quote-Fidelity Score Accuracy | Score matches human-annotated ground truth within ±0.15 on a 0-1 scale for 90% of test pairs | Score deviates by >0.2 from ground truth on verbatim quotes or clear fabrications | Compare model-assigned fidelity scores against 3 human annotator consensus scores on a stratified sample of exact, paraphrased, and fabricated quotes |
Speaker-Identity Disambiguation | Correctly attributes quote to the named speaker when multiple speakers appear in the same source, with >95% accuracy | Swaps speakers in audio transcripts with overlapping speech or assigns quote to wrong video participant | Test with multi-speaker audio transcripts and panel video captions where speakers are identified only by context clues, not explicit labels |
Context-Stripping Flag Precision | Flags context-stripping when >20% of surrounding qualifying language is omitted, with <10% false positive rate | Flags benign ellipsis or minor word omissions as context-stripping, or misses removal of negation words that invert meaning | Feed paired original-source and attributed-quote sets with known context alterations at 10%, 25%, and 50% omission levels |
Cross-Format Paraphrase Detection | Identifies paraphrased quotes across formats (text-to-audio, audio-to-text) with >85% recall | Treats a paraphrased spoken quote as an exact match to a written source, or marks a verbatim cross-format quote as mismatched | Test with quote pairs where the same statement appears verbatim in text and paraphrased in audio, plus control pairs with different meanings |
OCR Error Propagation Handling | Flags low-confidence OCR regions and requests original image review when character confidence <0.9 | Assigns high fidelity scores to quotes extracted from garbled OCR output without flagging extraction uncertainty | Feed screenshots with known OCR challenges (low resolution, unusual fonts, multi-column layouts) and verify that low-confidence regions trigger review flags |
Transcription Error Cascade Detection | Notes transcription confidence when spoken quote fidelity is assessed, and downgrades scores when transcript confidence is low | Treats a mistranscribed spoken quote as a fabrication rather than flagging the transcription layer as the error source | Test with audio clips containing domain terminology, accents, or background noise where ASR confidence is documented per segment |
Paraphrased-Claim-to-Verbatim-Source Matching | Correctly identifies that a paraphrased attributed quote matches the semantic content of a verbatim source with >80% accuracy | Requires exact string match for cross-format verification and marks semantically equivalent paraphrases as unverified | Use pairs where the attributed quote rephrases the source statement while preserving all factual claims and speaker intent |
Multi-Format Evidence Weighting | Assigns higher confidence to quotes verified against the original format source than against a format-converted intermediary | Weights a transcript-derived quote equally when verified against the transcript versus the original audio recording | Compare confidence scores when the same quote is verified against original audio vs. a third-party transcript of that audio |
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
Start with the base prompt and a single format pair (e.g., text transcript vs. text source). Remove structured output requirements initially—ask for a narrative verdict instead of JSON. Use a small set of 5–10 known quote pairs to iterate on instruction clarity.
Watch for
- The model accepting near-matches as exact matches without flagging paraphrase distance
- Missing speaker-identity disambiguation when multiple speakers share similar names
- Overly permissive context-stripping detection—test with deliberately truncated quotes

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