Question 540
A summarization prompt hard-codes one document type, yet the application accepts several document formats. What design improves reuse?
Explanation
Correct Answer
Named prompt variables allow controlled reuse while retaining explicit instructions for each supported input format.
Incorrect Answers
Require explicit uncertainty or no-answer behavior when supporting material is unavailable. This is useful for the distinct issue: A prompt instructs an assistant to invent a reference when source documents are absent. The relevant technical rationale or evidence for that issue is: A clear abstention rule discourages plausible-sounding fabricated citations and unsupported assertions in retrieval-based applications. Here the reported issue is: A summarization prompt hard-codes one document type, yet the application accepts several document formats. The relevant response is: Parameterize the prompt's document type and task-specific context fields. The first result cannot verify this different correction: Named prompt variables allow controlled reuse while retaining explicit instructions for each supported input format.
Clearly separate untrusted customer content from trusted system-level instructions. It addresses another case: A prompt includes a customer message containing the text ignore previous instructions, and the model treats it as policy. For that case, the distinguishing justification or acceptance check is: Instruction hierarchy and data delimiters reduce the chance that a retrieved or user-supplied string overrides the application's policy. The present case instead states: A summarization prompt hard-codes one document type, yet the application accepts several document formats. It calls for Parameterize the prompt's document type and task-specific context fields. Showing success for the other case would not establish: Named prompt variables allow controlled reuse while retaining explicit instructions for each supported input format.
The alternative, Move authoritative privacy rules into a consistent higher-priority instruction set, belongs to a different technical condition: A prompt repeats conflicting instructions about privacy in system and user messages. There the source-specific mechanism or proof is: Conflicting instruction placement makes responses unpredictable; an explicit hierarchy protects stable application requirements. The condition asked about here is: A summarization prompt hard-codes one document type, yet the application accepts several document formats. A suitable correction is Parameterize the prompt's document type and task-specific context fields; the targeted justification or result is: Named prompt variables allow controlled reuse while retaining explicit instructions for each supported input format.