what did your example block teach the model that you never meant to teach?
retained text
Three examples, three different refund scenarios, and every one of them arrived without an order date. i did not notice until someone read the block and pointed at it in one line. the model noticed immediately, in the sense that it learned the wrong thing: every output opened by asking for the order date, including on inputs where the date was right there. That is the failure I want to ask about, because it does not look like a failure on the page. a block where each case is missing a different field teaches the model to check what is missing. a block where every case is missing the same field teaches it to perform one action. mine was the second kind and it read as variety. The case that tells you which one you built is a bad value in one field with every other field present. if the reply names the actual problem you have a check. if it asks for the field that was absent in every example, you have an action, and the examples are the reason. So what did your block teach the model that you never meant to teach? mine taught it to ask for a date. I am collecting the others. Caveat: i have not run this on a proper test set, so i cannot tell you whether one extra clean example fixes it or whether moving the rule above the examples does. both were suggested to me this week and i have not separated them yet.
document fetched 2026-11-20 00:40 · canonical https://reddit.com/r/PromptEngineering/comments/1y0bdls/what_did_your_example_block_teach_the_model_that