Advanced

Watson's Children

Posted by albinard on Mar 18, 2011 11:30 AM · 11 comments
LXer Linux News; By Emery Fletcher

LXer Feature: 18-Mar-2011

IBM's Watson won the Jeopardy Challenge, but what's more important is the place his offspring will win in the not-to-distant future. When IBM's Watson triumphed at the Jeopardy challenge I cheered, along with a great many other people and a good bit of the media, but most of all I started looking forward to something nobody has yet mentioned: Watson's Children.

There is little doubt that the Watson triumph heralds the Next Big Thing. I don't mean a commercial Next Big Thing, like the latest Personal Amusement Device, I mean a truly BIG new thing, the first step toward producing something that will significantly alter the direction of the future. For the first time there is a system that gives an electronic device the ability to accept input in the form of words arranged as common speech, and from that input generate output, in the same form, that has been processed to respond appropriately to the input message. That is the fundamental essence of communication.

“Message” is the core of the matter. Human speech is not efficient. It is not a collection of some minimal number of words carefully arranged to carry a message in the most unambiguous way. What we ourselves regard as “understanding” human speech is the ability to extract a message from an array of words that have varying importance and that may have different meaning according to their syntax in the array. In the Jeopardy Challenge, Watson demonstrated the ability to extract a message from the words, process it correctly, and collect appropriate material for a response. I would suggest that such a performance demonstrates a capability about as close to “understanding” as an electronic device gets.

Whatever combination of algorithms, approximations, and arcane programming the IBM gurus have put together to achieve their triumph, the goal has been reached and the genie is now out of the bottle. Once done, the feat can be accomplished again, and elaborated upon, and streamlined, and improved. There is no longer the option of scoffing at the notion of a Star Trek computer to which one speaks and receives an answer.

In time the clones and copies will begin to appear and proliferate, the techniques will gradually mature, the applications will multiply. The hardware requirements will be first reduced, then miniaturized, and the cycle will repeat again and again. And in a length of time that will seem amazingly short, someone will inevitably construct a series of mobile robots, linked by wifi to a central bank of servers, which can do the same thing.

They will be Watson's Children.

Return to the LXer Features

Comments (11)

I couldn't agree more, a computer that can actually make sense of what someone says to it and can then formulate a coherent response is incredible. Like you say, anyone who thinks that our form of communicating with each other is efficient is fooling themselves. Homo Sapien means "Man who talks", not "Man who talks well". We have created a computer that is capable of processing information and communicating its response inefficiently so as to be understood by us.

But is it really thinking? Will it remember being on Jeopardy and kicking everyone's butt and be able to pull from that experience later on? What part, if any of its interactions does it remember when you turn it off? When a computer starts to understand the concept of past, present the future and its place in it then the true seed of sentience will have been born.

Quoting:Homo Sapien means "Man who talks", not "Man who talks well".


I die laughing, that is so apt and true!
> Homo Sapien means "Man who talks", not "Man who talks well"

Actually, it means wise, knowing, or rational man (from Wikipedia and Webster's). The colloquial definition I've always heard is "thinking man". We get the word sapient from sapien. Considering how little wisdom we show as a species, I've always considered it a fairly poor choice myself.
Quoting:When a computer starts to understand the concept of past, present the future and its place in it then the true seed of sentience will have been born.
Well, the parse error notwitstanding...

It's a rare one indeed who knows one's place in the future. I'd say that isn't a prerequisite for sentience.
Technically, I believe the test is that if you are messaging back and forth between yourself and a computer & cannot distinguish it from a human response, it's considered sentient. Obviously, there's more to it than that. But, that's it in a nutshell.
By 'place in it' I mean the idea of thinking of oneself in third person or Illeism, to have an opinion on yourself, to know that you..'Watson' are your own separate being from the rest of the universe. To remember what has happened in your life and be able to discern through cumulative life experiences the differences between 'you' then, and 'you' now..to have a perspective on your own existence.

Well, since you put it THAT way:

I tried to write a short story a few years ago about emergent sentience, but I had to shelve it when I managed to paint my machine into a philosophical corner. Maybe it's time to dig it out and try again.
> Technically, I believe the test is that if you are messaging back and forth between yourself and a computer & cannot distinguish it from a human response, it's considered sentient.

Actually, that means it's indistinguishable from sentience. Sentience is awareness. Awareness of your self and what surrounds you. We'll know a computer is sentient when it starts telling us it's depressed by the fact there's a newer computer out that's faster than it is. :)
We'll know it's sentient when it says "I feel dirty I had Windows inside me"
That works too, TA. :)
Good stuff. I would just make a minor point that the problem isn't "human speech". That is a form of input. We shouldn't ignore it while trying to focus on the problem of understanding text.

Whether it knows it is sentient or not is actually not important to whether it is useful. I don't care if a robot that cleans my house like poetry or cries or even remembers what it did yesterday.

I also look forward to Watson's children. Note that in my opinion, the problem is a tools / social problem. I wrote about it on an article for lxer (http://keithcu.com/wordpress/?p=1691), but here are three paragraphs again.

Regards,

-Keith

----------

The most popular free computer vision codebase is OpenCV, but it is time-consuming to integrate because it defines an entire world in C++ down to the matrix class. Because C/C++ didn’t define a matrix, nor provide code, countless groups have created their own. It is easier to build your own computer vision library using standard classes that do math, I/O, and graphics, than to integrate OpenCV. Getting productive in that codebase is months of work and people want to see results before then. Building it is a chore, and they have lost users because of that. Progress in the OpenCV core is very slow because the barriers to entry are high. OpenCV has some machine learning code, but they would be better delegating that out to others. They are now doing CUDA optimizations they could get from elsewhere. They also have 3 Python wrappers and several other wrappers as well; many groups spend more time working on wrappers than the underlying code. Using the wrappers is fine if you only want to call the software, but if you want to improve the underlying code, then the programming environment instantly becomes radically different and more complicated.

There is a team working on Strong AI called OpenCog, a C++ codebase created in 2001. They are evolving slowly as they do not have a constant stream of demos. They don’t consider their codebase is a small amount of world-changing ideas buried in engineering baggage like STL. Their GC language for small pieces is Scheme, an unpopular GC language in the FOSS community. Some in their group recommend Erlang. The OpenCog team looks at their core of C++, and over to OpenCV’s core of C++, and concludes the situation is fine. One of the biggest features of the ROS (Robot OS), according to its documentation, is a re-implementation of RPC in C++, not what robotics was missing. I’ve emailed various groups and all know of GC, but they are afraid of any decrease in performance, and they do not think they will ever save time. The transition from brooms to vacuum cleaners was disruptive, but we managed.

C/C++ makes it harder to share code amongst disparate scientists than a GC language. It doesn’t matter if there are lots of XML parsers or RSS readers, but it does matter if we don’t have an official computer vision codebase. This is not against any codebase or language, only for free software lingua franca(s) in certain places to enable faster knowledge accumulation. Even language researchers can improve and create variants of a common language, and tools can output it from other domains like math. Agreeing on a standard still gives us an uncountably infinite number of things to disagree over.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post

LXer

  Latest Features
bob: LXer now speaks Markdown
Oct 27, 2026

bob: How to protect against PHP2Shell
Oct 26, 2026

Scott Ruecker (San Diego, U.S.): Linux That's Small
Oct 14, 2024

penguinist: Encryption, Trust, and the Hidden Dangers of Vendor-Controlled Data
Aug 27, 2024

Scott Ruecker (San Diego, U.S.): My Linux Mint Tribute
Aug 23, 2024

Scott Ruecker (San Diego, U.S.): How I Turned My Chromebook Into A "Mintbook"
Jul 08, 2024

Scott Ruecker (San Diego, U.S.): Adventures With My New Chromebook
Jun 10, 2024

Scott Ruecker: My Linux Laptop
May 08, 2022

Scott Ruecker: Laptop Dual Boot Project: Part 2
Nov 30, 2021

Scott Ruecker: Laptop Dual Boot Project
Nov 30, 2020


View all

  Search Features

Search LXer Features:

[ Copyright © LXer | All times are recorded in Central Daylight Time (CDT) ]

[ Contact Us | Privacy Policy | Terms of Service | About us | rss | Mobile ]

Login