Unless someone's life is on the line, usually eyeballing the source URL is enough for me. If I'm looking for API documentation, there are a few well-known URLs I trust as authoritative. If I'm looking for product information, same thing. If the search engine points me to totallyawesomeproductleadgen19995.biz, I'm probably not getting reliable information.
An LLM response without explicit mention of its provenance... There's no way to even guess whether it is authoritative.
The sources will start to be redundant eventually. It's actually O(1) once you have looked at all the sources... that there are... in the world. Trivial!
I'm not sure. In this context, sources are utterances rather than speakers. So they're only finite if we limit ourselves to a snapshot of past utterances while doing our checking.
Wait, so if you go to python.org and the doc page says, "Added in version 3.11", you double-check this?
What do you even use for double-check? Some random low-quality content farm? A glitchy LLM? An dodgy mirror of official docs full of ads? Or do you actually dig the source code for this?
And do you keep double-checking with all other information on the page... "A TOMLDecodeError will be raised on an invalid TOML document." - are you going to start an interactive session and check which error will be raised?
Part of why I prefer to use a search engine is that I can see who is saying it, in what context. It might be Wikipedia, but also CIA world fact book. Or some blog but also python.org.
Or (lately) it might be AI SEO slop, reworded across 10 sites but nothing definitive. Which means I need to change my search strategy.
I find it easier (and quicker) to get to a believable result via a search engine than going via ChatGPT and then having to check what it claims.
You check the information you decide should be verified.