4 ms·
> Why are we drawing a difference between "prompt" and "context" exactly? Because they’re different things? The prompt doesn’t dynamically change. The context
by Aeolun 1y ago
> Why are we drawing a difference between "prompt" and "context" exactly?
Because they’re different things? The prompt doesn’t dynamically change. The context changes all the time.
I’ll admit that you can just call it all ‘context’ or ‘prompt’ if you want, because it’s essentially a large chunk of text. But it’s convenient to be able to distinguish between the two so you can talk about the same thing.
- __loam 1y agoIt's all the same blob of text in the api call
- FeepingCreature 1y agoThere's always been a distinction between prompt and data.
- oblio 1y agoSpoken like a non Lisp programmer.
- simonw 1y agoLLM's can't distinguish between instruction prompts and data prompts - that's why prompt injection attacks exist.
- FeepingCreature 1y agoI agree, and that's a problem. It doesn't mean the distinction doesn't exist, in fact it shows the opposite.
- chestervonwinch 1y agoThere is a conceptual difference between a blob of text drafted by a person and a dynamically generated blob of text initiated by a human, generated through multiple LLM calls that pull in information from targeted resources. Perhaps "dynamically generated prompts" is more fitting than "context", but nevertheless, there is a difference to be teased out, whatever the jargon we decide to use.