Your build starts here
Replace bracketed details with your own goal, context, and checks. Keep the first build small enough to inspect.
Help improve this importer-classification prompt: [current prompt]. Its actual policy is [required columns, value rules, duplicate policy, and allowed outcomes].
Identify one recurring ambiguity from these observed failures: [sanitized cases]. Create a small set of similar inputs whose correct outcomes differ because of that policy. Include a clearly accepted row, a near miss that must be rejected, an ambiguous case needing more information, and a quoted-text case that remains valid under the chosen CSV rules.
For every example, show the input, correct outcome, relevant policy clause, and a brief checkable explanation. Do not invent a new rule to make an example convenient. Keep proposed demonstration examples separate from fresh evaluation cases.
Return a revised example block and the smallest necessary instruction change. Describe how to compare it with the current prompt without claiming the new version has already been tested.Make this prompt yours
Use when one validation boundary causes repeatable errors. The policy and CSV parser behavior must already be defined.
You might also hear
- contrastive examples
- CSV validation prompt
- near-miss examples
The docs behind it
These references explain the underlying concepts and APIs. The prompt templates and project plans are original examples to adapt to your own setup.
Research sources reviewed .
Editorial review · October 28, 2026
Supported: Original, unexecuted classifier-template exercise. Its explicit fictional label policy and near-miss examples fit provider example guidance; no measured accuracy is implied.