I asked three different commercially available LLMs the same question:
Which TLDs have the same name as valid HTML5 elements?
This is a pretty simple question to answer. Take two lists and compare them. I know this question is possible to answer because I went through the lists two years ago. Answering the question was a little tedious and subject to my tired human eyes making no mistakes. So surely this is the sort of thing which an LLM excels at, right?
Wrong!
Here's how the three big beasts fared.
Good question! Let’s carefully check this.
[…Skip preamble…]
✅ Confirmed Matches
The following TLDs exactly match valid HTML5 element names:
- .audio → <audio>
- .code → <code>
- .link → <link>
- .menu → <menu>
- .nav → <nav>
- .video → <video>
This is wrong on two counts. First, it misses off several matches. Secondly, there is no .code
TLD! There is a .codes
, but that's not a match.
Gemini shits the bed completely:
Here are the top-level domains (TLDs) that have the same name as valid HTML5 elements:
- .address: The HTML <address> element is used to define the contact information for the author/owner of a document or an article.
- .article: The HTML <article> element specifies independent, self-contained content.
- .aside: The HTML <aside> element is used to define some content aside from the content it is placed in.
- .audio: The HTML <audio> element is used to embed sound content in a document.
- .body: The HTML <body> element defines the document's main content.
- […Skip a dozen more items…]
It just lists a bunch of HTML elements with no crossover to TLDs. Thanks Google. Thoogle.
Anthropic's AI does a half-arsed job.
Here are the TLDs that match HTML5 element names:Some other potential matches depend on how broadly you interpret "HTML5 elements":
- .audio - matches the <audio> element
- .video - matches the <video> element
- .data - matches the <data> element
- .link - matches the <link> element
- .menu - matches the <menu> element
- .style - matches the <style> element
- .select - matches the <select> element
- .app - while there's no <app> element in HTML5, there was discussion of it during HTML5 development
- .art - not a standard HTML element, though some frameworks use custom elements like this
The first seven are correct - although it ignores a dozen more correct answers. But then it does the LLM thing of trying to over-fit the data in a simulacrum of usefulness.
To be clear, I would expect a moderately intelligent teenager to be able to find two lists and compare them. If an intern gave me the same attention to detail as above, we'd be having a cosy little chat about their attitude to work.
I've discussed before why people have such dramatically different experiences using AI. For some it is an all-knowing and ineffable source of wisdom. For others, like me, it is mostly garbage.
I think it comes down to how familiar you are with the domain and its constraints. When I watch a medical drama, I have no idea if they're using realistic language. It sounds good, but real doctors probably cringe at the inaccuracies.
AI seems plausible because it relies on the Barnum Effect - it tells people what they want to hear. It produces words which sound correct.
We need a new term for Gell-Mann Amnesia. Something that describes how an AI is convincing if you don't understand its reasoning, and close to useless if you understand its limitations.