4 ms·
Your prompt paints a context that might keep it more on the rails, but it won't do multiple passes. This is probably the truth behind the black magic I’m imagi
by bloomingkales 2y ago
Your prompt paints a context that might keep it more on the rails, but it won't do multiple passes.
This is probably the truth behind the black magic I’m imagining. You could have it explicitly spit out this process, in which case you would see it’s first rough draft, followed by a “My first paragraph is probably wrong”, followed by a third paragraph where it attempts to fix the first paragraph. There is no outside RAG in this process.
The mumbo jumbo part of all this is that I’ve told it to “hide” this process from the user where it doesn’t explicitly output anything but its final answer, and the accuracy has been just as good (for my use case at least).
:Shrugs:
- jorl17 2y agoIsn't this in part what o1-preview is doing?
- block_dagger 2y agoYeah that’s not how next token prediction works. To actually do multiple passes you’d need to do that yourself, making multiple calls and feeding the responses back to the model.
- IanCal 2y agoWhy? The very nature of next token prediction means it's entirely capable of having that. It's not multiple passes, it's just one pass. You making multiple calls is just inserting fixed tokens then asking it to carry on completing.
- bloomingkales 2y agomaking multiple calls and feeding the responses back to the model. By asking it to reconsider half its generated response, aren’t I essentially asking it to formulate the second half of its response from the first half internally? I’m bypassing the manual process of feeding in the extra prompt. We are constantly having to tell the LLM close, but no cigar, iterate again, more or less.