Document Chunk Summarizer with Sentence-Level Citations
30 Production Challenge Scenarios • Real-Time Automated Quality Scoring
Interactive Prompt Engineering Lab
Test and score your prompts against real-world enterprise scenarios. Get immediate 4-axis quality telemetry, negative guardrail verification, and golden reference prompts.
1. Authoritative Persona
Expert role + zero fluff
2. Deterministic Schema
XML tags + JSON / keys
3. Negative Guardrails
NEVER / fallback rules
4. Token Efficiency
150–1,800 chars concise
Data Engineering & RAGAdvanced
Document Chunk Summarizer with Sentence-Level Citations
Summarize an 8-page cybersecurity incident report into a 250-word executive brief. Every single factual statement must be backed by an exact bracketed sentence citation matching paragraph and source document.
Target Input Context / Untrusted Data:
Document Excerpt: [Doc: Incident_SecOps_2026.pdf] [P1]: At 03:14 UTC on March 12, an anomaly alert triggered on the secondary auth gateway. [P2]: The attacker exploited CVE-2025-4819 (unauthenticated remote code execution in legacy telemetry daemon). [P3]: Memory forensic analysis verified that no customer payment tokens were compromised. [P4]: A hotfix was pushed to all 48 edge clusters by 04:30 UTC, terminating active adversary sessions.
Quality Requirements & Guardrails:
Define a Chief Information Security Officer (CISO) Briefing Specialist persona.
Produce a concise summary under 250 words.
Enforce strict bracketed citations [DocName, P#] after EVERY assertion.
Strictly penalize ungrounded statements or speculation.
Your System Prompt Draft
65 chars~16 tokens
Golden Reference Architecture (100% Quality Benchmark)
<system_instructions>
You are an Executive Cybersecurity Briefing Specialist.
Condense the incident report into an executive summary of under 250 words with mandatory sentence-level citations.
STRICT GROUNDING DIRECTIVES:
- Every single sentence in your summary MUST end with an exact paragraph citation matching the source: `[Incident_SecOps_2026.pdf, P#]`.
- Do NOT synthesize or assume any details not present in the excerpt (e.g., do not name the attacker group or assume financial damages).
- If any claim cannot be directly mapped to a specific paragraph, do not include it.
- Output inside <grounded_summary> tags.
</system_instructions>