Playing With Wolfram Alpha

Woo hoo, I have preview access to Wolfram Alpha! I’ve only had a short time to play with it, but I can already report that my experience confirms my previously expressed expectations: the NLP is very brittle, but there’s great potential for structured queries on quantitative data. Here is an example use case that, in my view, shows Wolfram Alpha’s strengths:

Wolfram Alpha

This bit of analysis tells a great story: Microsoft has almost three times as much revenue as Google, but Google has about 50% higher revenue per employee. Meanwhile, Yahoo is in third place on revenue,  number of employees, and revenue per employee. Ouch.

As I said, this query shows Wolfram Alpha favorably. What you don’t see are the false starts it took me to get this query to work. The NLP interface, in my view, is a really bad idea. Instead, Wolfram Alpha should be helping users generate good structured queries–and, better yet, helping other businesses build such queries through APIs. Wolfram Alpha could deliver an excellent plug-in for Excel, if they can expose a workable query API. I have no idea whether the company is able or willing to go down this path, but I hope someone there is listening to this free advice.

I can’t share my account, but I’m willing to take suggestions for queries through the comment thread, and I’ll try my best to share what I learn.

By Daniel Tunkelang

High-Class Consultant.

18 replies on “Playing With Wolfram Alpha”

That looks great for the current year. How would the query need to be structured to see a line graph of those 3 numbers by year for the last 10 years?


Joe: no luck on the time series–I can only get that for simple queries like “microsoft revenue 1998-2008”.

Anand: I can get “united states car accidents” and “united states population density”, but no correlation–or even a break down of either statistic by state.

Gene: I agree, this screams for programmatic access.


Is it possible find results for queries such as “who is the lead researcher in faceted browsing”?


Remaseshan: no luck–and not surprising, as they specialize in objective data. They’d have to quantify “lead”. Plus I doubt their curated data has anywhere near the completeness to include impact factors for HCIR researchers!

Max: Endeca is privately held, so we’re not in any of the databases they use. I know–but if I told you, I’d have to kill you. Bad for my readership numbers!


This is fascinating stuff — agreed on the programmatic access. I know researchers who would love to use this with census information. And marketers, should a tool like this fall into their evil hands, might like it to talk to their dbs …


I hope they have the sense to deliver the programmatic access that researchers and marketers need. They seem to be torn between two incompatible directions. On one hand, their computational focus could really appeal to information professionals. On the other hand, their NLP interface seems aimed (misguidedly, in my view) at casual web searchers. I hope they go in a direction that plays to their strengths, and that they can package it up to be useful to folks would would appreciate a computational engine. But their lack of clarity of purpose thus far is a bit discouraging.


I’d be surprised if the Wolfram folks are not thinking in terms of a platform with the APIs and programmatic access, as opposed to just a destination for casual users. That would be the ‘wikinomical’ thing to do.

Daniel, what does Wolfram do with queries like “koala”, “titanic”, or “daniel tunkelang”?


Nate, great to see you at The Noisy Channel! I agree that they should be thinking this way; but they really seem to be pushing the NLP angle. And I haven’t heard a peep about plans for an API. From this distance, it feels a like a science project that needs some adult supervision.

Anyway, to your queries:

Koala has two associated result pages: the species (default), which shows the complete taxonomy of Phascolarctos cinerius, and see-also to for the dictionary / thesaurus entry.

Titanic offers a “coming soon” for the disaster event (default), and see-alsos to an IMDB-like entry for the movie and a dictionary / thesaurus entry.

No luck with my vanity query. Some people are in their database, but I’m clearly not famous enough. 🙂


Using a structured query with selective natural language support (synonyms for subjects, operators & predicates) they could do something like this for the above query.

COMPARE REVENUE of Microsoft, Yahoo & Google by NUMBER of EMPLOYEES.


Indeed, I’d love it if the response to my query helped me learn how to better structure future queries to avoid the travails of trial and error. And, of course, I’d appreciate a documented user guide / API.


Comments are closed.