I’d be curious of the result.
But IMHO, since we’re in a “how to AI” thread… I believe what that is primarily testing isn’t the strength of the LLM model itself, but:
- whether this is a famous fact about your city that found its way into the training set (a factoid like how “Paris has one Eiffel Tower” that everybody knows)
- how good the “harness” is, the software around the LLM that helps it with complex information retrieval & analysis, by providing it non-LLM classical software tools that it can access (like a mapping utility or a database) — or not
- whether the particular AI brand/company you use wanted to provide such a capability — which is mostly a business and cost decision, because those workflows cost more money than something the model can just pull out of its training without external tooling
I think this is the sort of question that would be answerable relatively definitively with a harness like Claude Code or OpenAI Codex, but very difficult for a bare chatbot of any provider (except maybe Gemini? Google is building stronger integration between its AI and Google Maps; I haven’t tried it). But generally speaking, the chatbots don’t and can’t build themselves the tooling they need to properly investigate a question like this.
It’d be like locking the world’s best detective inside a closed room with no access any outside information, and asking him how many restaurants are in a city he’s never been to or heard of. LLMs can’t magically produce an answer for that out of nowhere either, without the harness giving them a way to look that up directly, or create for itself a way (like a small program) to do that lookup.
With an agentic coding harness (instead of a chatbot one), any recent, half-decent LLM would be able to write a geospatial lookup tool that defines a boundary polygon precisely out of government-provided census shapefiles that define a township (or some arbitrary boolean intersection of roads), combine that with a POI listing (or OpenStreetMap data), and do the right calculation to give you a correct table (assuming a sufficiently tight definition of “restaurant”, and a good enough source dataset).
You don’t need a particularly strong model for this, and even the weaker ones know how to do something like this, they just can’t because the typical chatbot experience essentially traps them in that locked room with very limited access to the outside. They can do simple web searches (which return results by relevant/SEO spamminess), but they can’t do a proper geospatial lookup like this because they are artificially constrained. That same model working in an appropriate harness will have much more freedom (and likely higher success rates) for something like this.
It’s the difference between:
- “Do a web search and try to find all the restaurants in my city” (the chatbot experience). I don’t think a human would succeed at this either, because it’s difficult/impossible to list ALL the restaurants from a search alone. It is an artificial constraint imposed by the chatbot experience, not because the AI is incapable.
- “Solve this same problem, using all the tools known to you, and you can write your own software to help you” (an agentic harness). It’s no longer limited to a web search and can do anything it needs, and pull data from anywhere it wants.
So all that is a very long-winded way to say that the AI providers provide not only different models, but also different harnesses to use to tackle different kinds of problems, but they don’t really guide you through the differences anywhere. You basically have to be a software developer to know that these other harnesses even exist, and when would be appropriate to use them vs a chatbot. These are productization failures, not necessarily LLM ones…