alt Hacker News> It's an LLM, it doesn't think. It's a machine that predicts the next token, given a sequence of tokens.
These can both be true, particularly when there is substantial state associated with each token prediction.
> It's an LLM, it doesn't think. It's a machine that predicts the next token, given a sequence of tokens.
These can both be true, particularly when there is substantial state associated with each token prediction.
> These can both be true, particularly when there is substantial state associated with each token prediction.
The state is entirely internal to the network and disappears after a token is generated, so I disagree, but, it isn't really the point I was trying to make. My point is these things are mechanical. You take an input, turn it into an embedding, feed it into a GPU along with a metric shit-ton of floating point weights, wait for a couple billion matrix multiplications, and get a new token out.
Stop the GPU, hit ctrl-c on the inference server, pull the power plug, cut the ethernet cable, send a kill signal, etc - any of these stop submitting new batches to the GPU and halt execution. That stops tokens from being generated. Stopping a "rogue" LLM is that easy. No input, no output.
It's not like a rat or another living creature that could chew its way out of a box just because it wants to. It's a calculator. You put tokens in, you get tokens out. You don't put tokens in... you don't get tokens out.