WEBVTT - Elementary, My Dear Watson

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.160 --> 0:00:08.920
<v Speaker 1>It's ready. Are you get in touch with technology with

0:00:09.039 --> 0:00:17.880
<v Speaker 1>tech Stuff from how stuff works dot com. Hello again, everyone,

0:00:17.920 --> 0:00:20.119
<v Speaker 1>Welcome to tech Stuff. My name is Chris Poulette and

0:00:20.120 --> 0:00:22.320
<v Speaker 1>I am an editor at how stuff works dot Com.

0:00:22.320 --> 0:00:25.760
<v Speaker 1>Sitting across from me, as always, is senior writer Jonathan Strickland.

0:00:25.920 --> 0:00:32.080
<v Speaker 1>The game is afoot Okay. This episode is about a

0:00:32.240 --> 0:00:37.320
<v Speaker 1>system created by IBM as a scientific experiment to determine

0:00:37.360 --> 0:00:41.640
<v Speaker 1>whether a computer can beat a human in a game

0:00:41.680 --> 0:00:47.680
<v Speaker 1>of skill and intelligence. Jonathan, what is Watson? That is correct?

0:00:49.640 --> 0:01:00.040
<v Speaker 1>I like all I would too? And Big Bucks? Are you?

0:01:00.400 --> 0:01:06.080
<v Speaker 1>Are you a giant computer? Sorry's really reaching back now.

0:01:06.120 --> 0:01:08.280
<v Speaker 1>I would like to tell you my sob story about

0:01:08.319 --> 0:01:11.000
<v Speaker 1>my life so I can win a new refrigerator. There.

0:01:11.120 --> 0:01:13.440
<v Speaker 1>That's reaching back, and it's really obscure. If you know

0:01:13.480 --> 0:01:16.200
<v Speaker 1>what I'm referring to with that particular game show, let

0:01:16.280 --> 0:01:18.480
<v Speaker 1>me know, sadly I do. So I'm just gonna stay

0:01:18.480 --> 0:01:20.520
<v Speaker 1>out at this. I'm not eligible to win. I read

0:01:20.520 --> 0:01:24.560
<v Speaker 1>the rules. So we're gonna talk today about the Watson computer.

0:01:24.680 --> 0:01:26.800
<v Speaker 1>We actually had a lot of listeners right in about

0:01:26.800 --> 0:01:30.320
<v Speaker 1>this because The announcement of the Watson computer came shortly

0:01:30.400 --> 0:01:33.800
<v Speaker 1>after we are episode on. Actually, I think it might

0:01:33.840 --> 0:01:36.760
<v Speaker 1>have even been just before our episode about Computers Versus

0:01:36.840 --> 0:01:40.080
<v Speaker 1>Humans published, So of course it looked like we had

0:01:40.080 --> 0:01:46.440
<v Speaker 1>a glaring omission. Yes, but by in our defense, we

0:01:46.480 --> 0:01:49.360
<v Speaker 1>didn't know about it yet. Yes, actually we mentioned one

0:01:49.400 --> 0:01:59.320
<v Speaker 1>of Watson's cousins predecessors, is probably a predecessor of processors. Yeah. Actually, um,

0:01:59.440 --> 0:02:02.480
<v Speaker 1>deep Blue, I'm sorry, Deep Blue, Deep Blue, Big Blue

0:02:02.480 --> 0:02:05.200
<v Speaker 1>would be the company that made it. But the the

0:02:07.640 --> 0:02:10.640
<v Speaker 1>we're talking about IBM, and IBM does this thing occasionally

0:02:10.720 --> 0:02:13.600
<v Speaker 1>where they issue Yeah, well it is a thing, I mean,

0:02:13.639 --> 0:02:16.880
<v Speaker 1>it's it's because it's not just Deep Blue, it's not

0:02:16.960 --> 0:02:21.600
<v Speaker 1>just Watson. They issue what they call grand challenges their

0:02:21.639 --> 0:02:25.160
<v Speaker 1>engineering teams. Yes, they've had a series of these, and

0:02:25.400 --> 0:02:29.320
<v Speaker 1>some of them are are more noticeable to the public,

0:02:29.360 --> 0:02:32.120
<v Speaker 1>I guess, and others. Deep Blue would definitely be one

0:02:32.160 --> 0:02:34.959
<v Speaker 1>of those because that made headlines. In the nineties. Deep

0:02:34.960 --> 0:02:39.040
<v Speaker 1>Blue was of course the computer that challenged Gary Kasparov,

0:02:39.280 --> 0:02:44.600
<v Speaker 1>the chess grand Master um to a series of games.

0:02:44.880 --> 0:02:48.840
<v Speaker 1>In the first series of games, Kasparov was emerged victorious,

0:02:48.840 --> 0:02:52.320
<v Speaker 1>and in the second Deep blue one, and so that

0:02:52.440 --> 0:02:54.240
<v Speaker 1>was one of those things that kind of propelled the

0:02:54.240 --> 0:02:58.120
<v Speaker 1>whole idea of computers being able to outwit humans, to

0:02:58.120 --> 0:03:02.200
<v Speaker 1>be able to outperform humans in certain tasks. But there

0:03:02.200 --> 0:03:05.320
<v Speaker 1>were other tasks that humans were still much much more

0:03:05.440 --> 0:03:10.280
<v Speaker 1>capable of completing than computers. And UM, as it turns out,

0:03:10.280 --> 0:03:13.440
<v Speaker 1>Watson is a grand challenge. To answer one of those,

0:03:14.040 --> 0:03:16.320
<v Speaker 1>so to speak, or maybe question one of those would

0:03:16.320 --> 0:03:17.520
<v Speaker 1>be better because you have to put it in the

0:03:17.520 --> 0:03:20.320
<v Speaker 1>form of a question, right, That's that's correct. UM. I

0:03:20.320 --> 0:03:23.480
<v Speaker 1>would imagine that Watson does this flawlessly. But we could

0:03:23.480 --> 0:03:26.080
<v Speaker 1>talk about the differences in a human opponent and a

0:03:26.120 --> 0:03:28.760
<v Speaker 1>computer opponent in a little bit. UM. I wanted to

0:03:28.760 --> 0:03:31.040
<v Speaker 1>get into some of the details. Watson is not actually

0:03:31.400 --> 0:03:35.920
<v Speaker 1>a single computer as I typically think about it. UM.

0:03:35.960 --> 0:03:38.880
<v Speaker 1>It is made of ten racks of IBM power, seven

0:03:38.880 --> 0:03:42.560
<v Speaker 1>fifty servers using the Linux operating system. How many cores

0:03:42.720 --> 0:03:46.520
<v Speaker 1>does it have? Two thousand, eight hundred eight processor cores

0:03:46.800 --> 0:03:50.880
<v Speaker 1>wholly free holies? Have you thought your quad core processor

0:03:51.120 --> 0:03:55.040
<v Speaker 1>was the bees knees? I also thought my, uh my

0:03:55.160 --> 0:04:00.360
<v Speaker 1>computers for gigabytes of RAM were pretty much for what

0:04:00.400 --> 0:04:04.520
<v Speaker 1>I'm doing. But Watson has fifteen terabytes of RAM. A

0:04:04.640 --> 0:04:10.000
<v Speaker 1>terabyte is one thousand, twenty four gigabytes, that's right. Also,

0:04:10.880 --> 0:04:14.040
<v Speaker 1>it computes eight at the rate of eighty tarra flops,

0:04:14.120 --> 0:04:19.240
<v Speaker 1>which is eighty trillion calculations per second. And in fact,

0:04:20.200 --> 0:04:23.960
<v Speaker 1>I understand from reading IBM's website about Watson that it

0:04:24.080 --> 0:04:29.120
<v Speaker 1>has somewhere in the neighborhood of two million books essentially.

0:04:29.160 --> 0:04:30.960
<v Speaker 1>I mean, that's it's it's kind of hard to say

0:04:31.000 --> 0:04:34.720
<v Speaker 1>how much information is in a book, but um more

0:04:34.760 --> 0:04:36.640
<v Speaker 1>or less two million books, and it can scan the

0:04:36.839 --> 0:04:42.000
<v Speaker 1>entirety of information on all of those hard drives in

0:04:42.040 --> 0:04:46.760
<v Speaker 1>that machine in roughly two to three second. Right. The

0:04:46.800 --> 0:04:49.679
<v Speaker 1>idea here is that they needed to create a computer.

0:04:49.960 --> 0:04:51.800
<v Speaker 1>You have, the whole the whole challenge here was to

0:04:51.800 --> 0:04:54.200
<v Speaker 1>create a computer that could compete in a game of

0:04:54.279 --> 0:04:57.800
<v Speaker 1>Jeopardy and compete on a championship level. Yeah. And as

0:04:57.839 --> 0:04:59.960
<v Speaker 1>a matter of fact, when we talked about the computer

0:05:00.120 --> 0:05:06.000
<v Speaker 1>to versus person challenge in that podcast, we were discussing how,

0:05:06.440 --> 0:05:09.040
<v Speaker 1>you know, computers do some things really really well and

0:05:09.120 --> 0:05:11.160
<v Speaker 1>some things they don't do so well. And ib AM

0:05:11.200 --> 0:05:14.360
<v Speaker 1>freely admitted that this was a real toughie. Yeah, because

0:05:14.400 --> 0:05:16.200
<v Speaker 1>as it turns out one of the things computers do

0:05:16.240 --> 0:05:19.200
<v Speaker 1>really well. They do well with things like like logical problems,

0:05:19.800 --> 0:05:23.480
<v Speaker 1>you know, because you follow a very set a series

0:05:23.480 --> 0:05:28.440
<v Speaker 1>of steps, things that that obey specific rules. The English

0:05:28.560 --> 0:05:35.480
<v Speaker 1>language does not obey rules as strictly as a mathematical formula. Yes,

0:05:36.160 --> 0:05:38.400
<v Speaker 1>as a matter of fact, we we sort of go

0:05:38.560 --> 0:05:42.200
<v Speaker 1>with with things that might be tricky for computers to

0:05:42.240 --> 0:05:45.000
<v Speaker 1>understand all the time because we constantly on this show

0:05:45.040 --> 0:05:49.360
<v Speaker 1>do wordplay and puns, um, and computers may not necessarily

0:05:49.440 --> 0:05:52.680
<v Speaker 1>understand the nuances of such things, or or slang, or

0:05:52.760 --> 0:05:57.120
<v Speaker 1>metaphors or metaphors. Um. There's a lot of elements to

0:05:57.200 --> 0:06:00.640
<v Speaker 1>human speech that we naturally understand as we develop our

0:06:00.720 --> 0:06:03.599
<v Speaker 1>language skills. Right speak for yourself, I have no idea

0:06:03.640 --> 0:06:07.279
<v Speaker 1>how this thing works, okay, but most of us figure

0:06:07.279 --> 0:06:11.280
<v Speaker 1>out how to determine what someone is talking about based

0:06:11.360 --> 0:06:15.280
<v Speaker 1>on contextual clues and our knowledge of things like wordplay

0:06:15.320 --> 0:06:18.400
<v Speaker 1>and metaphors. So as we build our vocabulary, as we

0:06:18.440 --> 0:06:23.040
<v Speaker 1>build our ability to create sentences, as we understand concepts

0:06:23.080 --> 0:06:28.000
<v Speaker 1>that are not necessarily concrete, then we are able to

0:06:28.080 --> 0:06:33.240
<v Speaker 1>communicate in a more ambiguous way than a computer would

0:06:33.279 --> 0:06:37.640
<v Speaker 1>necessarily be capable of on any normal computer. That is, So,

0:06:37.680 --> 0:06:39.919
<v Speaker 1>what are you trying to say, Johnny get Yeah, what

0:06:39.960 --> 0:06:41.640
<v Speaker 1>I'm trying to say is that I'm trying to say

0:06:41.680 --> 0:06:45.160
<v Speaker 1>is that the depending on the way you word a sentence, Uh,

0:06:45.240 --> 0:06:48.080
<v Speaker 1>a human might be able to determine immediately what the

0:06:48.120 --> 0:06:51.240
<v Speaker 1>significance is of the sentence. You know, what you just said.

0:06:51.240 --> 0:06:53.640
<v Speaker 1>They'd be able to understand it. A computer, depending upon

0:06:53.640 --> 0:06:56.159
<v Speaker 1>the wording, may not be able to interpret it properly

0:06:56.240 --> 0:06:59.839
<v Speaker 1>because you know, you didn't necessarily say like, the ball

0:07:00.120 --> 0:07:03.280
<v Speaker 1>is blue. You know, you might have used a much

0:07:03.320 --> 0:07:06.160
<v Speaker 1>more poetic way of saying it that a computer just

0:07:06.200 --> 0:07:09.479
<v Speaker 1>can't you know, the computer can't equate that as being

0:07:09.560 --> 0:07:11.880
<v Speaker 1>the ball is blue. But any human listener would be

0:07:12.760 --> 0:07:15.040
<v Speaker 1>able to understand what you were getting at and say, oh,

0:07:15.080 --> 0:07:17.400
<v Speaker 1>it's a blue ball. It was just a really fancy,

0:07:17.520 --> 0:07:21.680
<v Speaker 1>flowery way of saying that. Yes, Um, I watched a

0:07:21.760 --> 0:07:24.880
<v Speaker 1>number of videos on the IBM site and some of

0:07:24.880 --> 0:07:29.160
<v Speaker 1>them are quite amusing. Actually, uh, because the early versions

0:07:29.160 --> 0:07:32.600
<v Speaker 1>of Watson just didn't get it. Yeah, they weren't. They

0:07:32.600 --> 0:07:37.080
<v Speaker 1>weren't the most um accurate. And what what's funny about

0:07:37.160 --> 0:07:39.760
<v Speaker 1>is not that the computer didn't get it. But the

0:07:39.880 --> 0:07:43.600
<v Speaker 1>looks on the engineer's faces and as they were going, yeah, okay, no,

0:07:43.760 --> 0:07:45.920
<v Speaker 1>maybe not not so much. We have to go back

0:07:45.960 --> 0:07:50.440
<v Speaker 1>to the drawing board. But Dr Chris Welty was saying

0:07:50.640 --> 0:07:53.600
<v Speaker 1>the point of this exercise is to do the science

0:07:54.120 --> 0:07:57.560
<v Speaker 1>behind this and and they specifically we're looking forward to

0:07:57.640 --> 0:08:01.880
<v Speaker 1>the challenge of Jeopardy and UM. You know, if you

0:08:02.520 --> 0:08:05.040
<v Speaker 1>if you're unfamiliar with the show UM, which some of

0:08:05.080 --> 0:08:08.520
<v Speaker 1>you maybe uh a lot of the questions. Of course,

0:08:08.560 --> 0:08:12.840
<v Speaker 1>the the the answers are presented first. UH. The contestants

0:08:12.840 --> 0:08:15.520
<v Speaker 1>are given the opportunity to choose one of six categories

0:08:15.520 --> 0:08:19.600
<v Speaker 1>that are on the board at different values UH monetary

0:08:19.640 --> 0:08:24.000
<v Speaker 1>values UM. And so you can expect in these categories

0:08:24.040 --> 0:08:27.160
<v Speaker 1>that the the answers UH you are actually supposed to

0:08:27.160 --> 0:08:28.920
<v Speaker 1>give the question if you are contestant on the game.

0:08:29.080 --> 0:08:33.400
<v Speaker 1>The answers can fall within a certain domain of knowledge UM.

0:08:33.440 --> 0:08:38.040
<v Speaker 1>For example, the infamous Potent Potables category UM is about

0:08:38.200 --> 0:08:41.480
<v Speaker 1>alcoholic drinks, and you can expect that if you are

0:08:41.640 --> 0:08:44.560
<v Speaker 1>fairly knowledgeable about different kinds of drinks that you might

0:08:44.840 --> 0:08:47.839
<v Speaker 1>do well or poorly in the category. So you should

0:08:47.840 --> 0:08:52.920
<v Speaker 1>either choose questions or answers from the category or not. Um. Well,

0:08:53.280 --> 0:08:55.240
<v Speaker 1>you know, if no one has bothered to program that

0:08:55.280 --> 0:08:59.440
<v Speaker 1>information into Watson, Uh, then Watson will do poorly in

0:08:59.440 --> 0:09:03.920
<v Speaker 1>that category. But some of the categories on Jeopardy are

0:09:03.920 --> 0:09:05.959
<v Speaker 1>written with a lot of word smithing involved, so you

0:09:06.040 --> 0:09:09.640
<v Speaker 1>might have to supply an answer that rhymes or unscramble

0:09:09.840 --> 0:09:13.120
<v Speaker 1>the war letters to do to form another word. Now,

0:09:13.120 --> 0:09:17.240
<v Speaker 1>the unscrambling thing might come very easy to a computer, um,

0:09:17.280 --> 0:09:20.960
<v Speaker 1>but the rhyming answer, you'd have to go over a

0:09:20.960 --> 0:09:23.360
<v Speaker 1>lot of synonyms in your head to try to find. Okay, well,

0:09:23.400 --> 0:09:25.960
<v Speaker 1>I know the answer to this question, but it obviously

0:09:26.000 --> 0:09:29.600
<v Speaker 1>isn't going to rhyme right. So um. Dr Welty said,

0:09:29.720 --> 0:09:31.000
<v Speaker 1>you know, this is one of the things that we

0:09:31.000 --> 0:09:33.920
<v Speaker 1>were really looking forward to. We wanted, we wanted to challenge.

0:09:33.920 --> 0:09:36.439
<v Speaker 1>We wanted the computer to be answered able to answer

0:09:36.559 --> 0:09:40.839
<v Speaker 1>questions or question answers that the computer normally wouldn't be

0:09:40.880 --> 0:09:43.200
<v Speaker 1>able to. So they were really looking forward to cracking

0:09:43.200 --> 0:09:46.640
<v Speaker 1>this nut, so to speak. Um. They talked about there

0:09:46.640 --> 0:09:50.400
<v Speaker 1>being five major areas that they had to concentrate on

0:09:50.480 --> 0:09:54.280
<v Speaker 1>in order to make Watson work based upon the way

0:09:54.360 --> 0:09:59.600
<v Speaker 1>Jeopardy works, because again they designed this project with a

0:09:59.679 --> 0:10:02.640
<v Speaker 1>very specific application in mind. It helped give them direction

0:10:02.720 --> 0:10:04.640
<v Speaker 1>as opposed to it just being I just want to

0:10:04.679 --> 0:10:08.520
<v Speaker 1>make a computer that is able to analyze semantics and

0:10:08.520 --> 0:10:11.439
<v Speaker 1>and respond. Um. That's you know, that's a much more

0:10:11.480 --> 0:10:14.240
<v Speaker 1>general approach. By giving them the fact that, okay, well,

0:10:14.280 --> 0:10:16.240
<v Speaker 1>our goal is to be able to create a computer

0:10:16.280 --> 0:10:21.200
<v Speaker 1>that can compete and potentially beat champions in Jeopardy, Uh,

0:10:21.360 --> 0:10:24.480
<v Speaker 1>it provided more focus. So with Jeopardy in mind, they

0:10:24.480 --> 0:10:26.360
<v Speaker 1>said the five things they needed to concentrate on was

0:10:26.360 --> 0:10:30.560
<v Speaker 1>that Jeopardy creates a broad and open domain, which means

0:10:30.600 --> 0:10:34.200
<v Speaker 1>that you don't just get questions about one subject. Yes,

0:10:34.280 --> 0:10:35.760
<v Speaker 1>you're not going to have to know everything there is

0:10:35.800 --> 0:10:38.000
<v Speaker 1>to know about alcoholic drinks and that's the only thing

0:10:38.040 --> 0:10:39.760
<v Speaker 1>you were going to be asked about. Right There might

0:10:39.800 --> 0:10:46.120
<v Speaker 1>be politics, pop culture, sports, literature, all sorts of categories

0:10:46.120 --> 0:10:49.080
<v Speaker 1>that you could potentially come up against. So with that

0:10:49.120 --> 0:10:51.720
<v Speaker 1>in mind, the computer had to be able to answer

0:10:51.760 --> 0:10:56.360
<v Speaker 1>those things. Uh. There were as Chris was saying, there

0:10:56.440 --> 0:11:01.560
<v Speaker 1>was an element of complex language. Jeopardy answers can be tricky.

0:11:02.000 --> 0:11:04.520
<v Speaker 1>They're not necessarily straightforward. It's kind of like the New

0:11:04.559 --> 0:11:07.360
<v Speaker 1>York Times crossword puzzle. If you read the clues to

0:11:07.400 --> 0:11:11.760
<v Speaker 1>that crossword puzzle, they aren't necessarily straightforward. They require you

0:11:11.840 --> 0:11:15.160
<v Speaker 1>to make some You have to bridge some gaps in

0:11:15.240 --> 0:11:18.760
<v Speaker 1>order to get to the right answer yes. And in fact,

0:11:18.840 --> 0:11:22.040
<v Speaker 1>they will ask you even in clues for for that puzzle.

0:11:22.120 --> 0:11:24.680
<v Speaker 1>They will ask you for things in poetic language, and

0:11:24.720 --> 0:11:26.760
<v Speaker 1>you'll have to think about things in a completely different

0:11:26.760 --> 0:11:30.880
<v Speaker 1>way than you might have otherwise. The next area that

0:11:30.920 --> 0:11:33.560
<v Speaker 1>they had to focus on was high precision, so you

0:11:33.600 --> 0:11:37.559
<v Speaker 1>had to be able to narrow down your choices and

0:11:37.640 --> 0:11:41.679
<v Speaker 1>find out which of your potential answers would be the most,

0:11:42.240 --> 0:11:46.160
<v Speaker 1>the most accurate, or the best one to choose. Along

0:11:46.200 --> 0:11:49.000
<v Speaker 1>with that was accurate confidence, which means that the computer

0:11:49.040 --> 0:11:52.000
<v Speaker 1>itself has to be able to determine how likely is

0:11:52.080 --> 0:11:56.000
<v Speaker 1>this answer? How likely is this the right answer? Yes? Right,

0:11:56.400 --> 0:11:58.760
<v Speaker 1>and um. And then the last one was high speed.

0:11:58.760 --> 0:12:01.200
<v Speaker 1>It had to be a really really fast computer in

0:12:01.280 --> 0:12:04.880
<v Speaker 1>order to compete against people, because if you know something,

0:12:05.120 --> 0:12:07.920
<v Speaker 1>you just you just spout it out right, you know,

0:12:07.960 --> 0:12:11.559
<v Speaker 1>you you buzz and you say, who is Marshall brain?

0:12:12.200 --> 0:12:14.840
<v Speaker 1>You know? And then you've got the answer, who is

0:12:15.280 --> 0:12:18.120
<v Speaker 1>Marshal brain? I think only one person can answer that question,

0:12:18.360 --> 0:12:21.680
<v Speaker 1>and he is not in the studio today. UM. But yeah,

0:12:21.720 --> 0:12:26.559
<v Speaker 1>you have to have computers capable of of accessing all

0:12:26.600 --> 0:12:29.560
<v Speaker 1>this information and picking it out as quickly as a

0:12:29.600 --> 0:12:32.480
<v Speaker 1>human would be able to. UM. In fact, I saw

0:12:32.520 --> 0:12:36.280
<v Speaker 1>on one of these videos that uh, if you had

0:12:36.960 --> 0:12:42.680
<v Speaker 1>a two point six giga Hurts core processor a computer

0:12:42.760 --> 0:12:45.280
<v Speaker 1>running one of those Okay, posably, I do own a

0:12:45.280 --> 0:12:47.719
<v Speaker 1>computer with a two point six gigga Hurts process right,

0:12:47.800 --> 0:12:49.920
<v Speaker 1>so you know, kind of a middle of the road

0:12:50.000 --> 0:12:53.880
<v Speaker 1>computer right now. But but two point six gigga Hurts computer.

0:12:53.920 --> 0:12:57.960
<v Speaker 1>If you were to try and answer one question uh,

0:12:57.960 --> 0:13:02.679
<v Speaker 1>and you were going to go through all of Watson's

0:13:03.000 --> 0:13:06.319
<v Speaker 1>UH data in order to find that question, the answer

0:13:06.360 --> 0:13:08.839
<v Speaker 1>to that question and compare all the answers and come

0:13:08.920 --> 0:13:12.120
<v Speaker 1>up with the best result and then presented, it would

0:13:12.120 --> 0:13:15.959
<v Speaker 1>take you two hours for that one computer. It doesn't

0:13:15.960 --> 0:13:19.199
<v Speaker 1>surprise me much. So that's why you have that two

0:13:19.240 --> 0:13:23.840
<v Speaker 1>thousand eight processor. You know that with all the different

0:13:23.920 --> 0:13:26.800
<v Speaker 1>uh the web servers running, you have to have those

0:13:26.840 --> 0:13:30.280
<v Speaker 1>core processors running so that you can solve these questions

0:13:30.320 --> 0:13:33.719
<v Speaker 1>in parallel. Excuse me, And you probably remember us talking

0:13:33.760 --> 0:13:37.600
<v Speaker 1>about parallel computing and other podcasts. That's the idea that

0:13:37.640 --> 0:13:39.680
<v Speaker 1>you try and solve a problem by working on parts

0:13:39.720 --> 0:13:42.080
<v Speaker 1>of the problem all at the same time. In this case,

0:13:42.640 --> 0:13:47.679
<v Speaker 1>Watson gets the the answer from Jeopardy and then goes

0:13:47.760 --> 0:13:51.520
<v Speaker 1>through and tries to process all the potential questions that

0:13:51.600 --> 0:13:54.640
<v Speaker 1>would be the correct response to that answer, and then

0:13:54.640 --> 0:13:56.920
<v Speaker 1>it has to evaluate them and choose the right one,

0:13:57.360 --> 0:13:59.520
<v Speaker 1>and has to do this in just a couple of seconds.

0:14:00.960 --> 0:14:06.720
<v Speaker 1>It's a pretty cool idea. The the challenges are not trivial,

0:14:09.679 --> 0:14:14.560
<v Speaker 1>the answers are, but not the the challenges um and

0:14:14.600 --> 0:14:16.800
<v Speaker 1>like you were saying, the early tests were very amusing

0:14:16.840 --> 0:14:19.880
<v Speaker 1>because Watson just didn't get it. It would it would

0:14:19.880 --> 0:14:23.560
<v Speaker 1>give answers that were obviously related to the question, or

0:14:23.600 --> 0:14:26.760
<v Speaker 1>at least related to words that were within the question,

0:14:26.800 --> 0:14:29.760
<v Speaker 1>but we're not the right answer. It's kind of like

0:14:29.800 --> 0:14:31.920
<v Speaker 1>if you were ever using a search engine and you

0:14:32.000 --> 0:14:35.360
<v Speaker 1>put in certain terms and the results you're getting back

0:14:35.920 --> 0:14:38.240
<v Speaker 1>are related to the terms you put in, but not

0:14:38.280 --> 0:14:42.080
<v Speaker 1>to the subject matter you wanted, because it's maybe using hominem's,

0:14:42.240 --> 0:14:45.960
<v Speaker 1>or it's using synonyms, or it's or maybe you misspelled

0:14:46.000 --> 0:14:48.400
<v Speaker 1>something or whatever. But anyway, you're getting the wrong kind

0:14:48.400 --> 0:14:53.840
<v Speaker 1>of responses, same sort of thing. Yep. And speaking of trivial,

0:14:54.160 --> 0:14:56.800
<v Speaker 1>I did want to point out to that Dr Kelly,

0:14:56.920 --> 0:14:59.040
<v Speaker 1>Dr John E. Kelly the third He is a senior

0:14:59.120 --> 0:15:01.760
<v Speaker 1>vice president of ib i'm in the director of IBM Research.

0:15:02.480 --> 0:15:06.480
<v Speaker 1>Um this the project itself, you know, Yes, they're building

0:15:06.520 --> 0:15:10.680
<v Speaker 1>a computer to win a trivia contest, so that might

0:15:10.800 --> 0:15:16.360
<v Speaker 1>seem trivial. Yes, However, the point is, you know, Dr

0:15:16.440 --> 0:15:20.800
<v Speaker 1>Kelly was saying, Look, the amount of information that is

0:15:20.960 --> 0:15:27.840
<v Speaker 1>being created today is rapidly uh, overcoming our ability to

0:15:29.160 --> 0:15:31.960
<v Speaker 1>identify it, process it, makes sense of it, and and

0:15:31.960 --> 0:15:34.840
<v Speaker 1>and derive knowledge from it. Yeah. In fact, I think

0:15:34.880 --> 0:15:38.520
<v Speaker 1>it is a fifteen petabytes of data raw data get

0:15:38.560 --> 0:15:41.240
<v Speaker 1>generated every day, not just not just from people but

0:15:41.280 --> 0:15:44.520
<v Speaker 1>from machines as well. But that's that's an insane amount

0:15:44.520 --> 0:15:47.000
<v Speaker 1>of information. Yes, yes, now, I mean, the human mind

0:15:47.040 --> 0:15:49.200
<v Speaker 1>is a remarkable thing, and if you have systems in place,

0:15:49.240 --> 0:15:53.240
<v Speaker 1>you can help manage that. But at some point, uh,

0:15:53.280 --> 0:15:55.160
<v Speaker 1>you know, even even people can't keep up with that.

0:15:55.200 --> 0:15:59.800
<v Speaker 1>Even there are remarkable computing machines and our skulls. So uh,

0:15:59.840 --> 0:16:03.200
<v Speaker 1>the idea is to build a tool that can actually

0:16:03.400 --> 0:16:06.960
<v Speaker 1>help people. There will be a tool for people to

0:16:06.960 --> 0:16:10.880
<v Speaker 1>help people make sense of this vast amount of information

0:16:11.360 --> 0:16:13.800
<v Speaker 1>and and to overcome that and get get real help

0:16:13.840 --> 0:16:19.720
<v Speaker 1>I guess from machines and and help people understand or

0:16:19.840 --> 0:16:23.920
<v Speaker 1>navigate the world of information that is rapidly creating. UM.

0:16:24.120 --> 0:16:26.400
<v Speaker 1>One of the cooler videos on this site I think

0:16:27.400 --> 0:16:29.520
<v Speaker 1>was the one where they were explaining, look, there there's

0:16:29.560 --> 0:16:33.640
<v Speaker 1>always been this interconnected system of information going on all

0:16:33.680 --> 0:16:36.560
<v Speaker 1>over the world, but we didn't really understand it nearly

0:16:36.600 --> 0:16:40.560
<v Speaker 1>as well. Until the Internet came around. We could actually

0:16:40.640 --> 0:16:43.560
<v Speaker 1>see what was going on, you know, in seconds, rather

0:16:43.600 --> 0:16:47.120
<v Speaker 1>than you know, having it take hours or days or

0:16:47.160 --> 0:16:52.120
<v Speaker 1>weeks or months or even years in many many years past. UM,

0:16:52.440 --> 0:16:56.240
<v Speaker 1>and it's it's just enabled this and is accelerating the problem.

0:16:56.320 --> 0:17:00.400
<v Speaker 1>So UM, the challenge of creating the computer to play

0:17:00.400 --> 0:17:03.440
<v Speaker 1>the game, well, this is basically, I guess an exercise

0:17:03.600 --> 0:17:06.359
<v Speaker 1>to see can we really do this? Can we create

0:17:07.080 --> 0:17:12.600
<v Speaker 1>uh reasonably intelligent computer that can help us, you know,

0:17:12.640 --> 0:17:16.119
<v Speaker 1>figure out what's going on and where the the answers

0:17:16.119 --> 0:17:18.919
<v Speaker 1>are to our questions? Can can we create a computer

0:17:19.000 --> 0:17:23.960
<v Speaker 1>that can understand natural language so that that you challenge it, right,

0:17:24.160 --> 0:17:27.000
<v Speaker 1>It's it's not it's not that you have to tailor

0:17:27.080 --> 0:17:29.480
<v Speaker 1>your language to the computer so that it understands I mean,

0:17:29.560 --> 0:17:31.720
<v Speaker 1>we were familiar with that. You know, we talked about

0:17:31.720 --> 0:17:34.880
<v Speaker 1>Boollyan logic before, about how if you want to do

0:17:35.160 --> 0:17:38.600
<v Speaker 1>really effective search terms, you need to understand how Booleyan

0:17:38.640 --> 0:17:41.280
<v Speaker 1>logic works so that you can. Because search engines don't

0:17:41.359 --> 0:17:45.080
<v Speaker 1>understand natural language, they'll do their best to try and

0:17:45.119 --> 0:17:48.520
<v Speaker 1>match your query with the right result, but they don't

0:17:48.600 --> 0:17:53.040
<v Speaker 1>understand it. They aren't able to analyze the information. One

0:17:53.080 --> 0:17:56.520
<v Speaker 1>of the concepts that it was really important with Watson

0:17:56.920 --> 0:17:58.879
<v Speaker 1>is one that's going to be very important if we

0:17:58.960 --> 0:18:02.160
<v Speaker 1>ever are to have us semantic web, which is the

0:18:02.200 --> 0:18:06.080
<v Speaker 1>idea that you could talk to your computer, whether you're

0:18:06.240 --> 0:18:09.240
<v Speaker 1>actually speaking or typing or whatever. You you can communicate

0:18:09.240 --> 0:18:11.840
<v Speaker 1>with your computer in a natural way, and the computer

0:18:11.880 --> 0:18:14.880
<v Speaker 1>will be able to understand, at least on some level.

0:18:15.040 --> 0:18:17.160
<v Speaker 1>It may not be a deep level, but be able

0:18:17.160 --> 0:18:20.480
<v Speaker 1>to interpret what you're saying and give you the right result.

0:18:21.000 --> 0:18:24.600
<v Speaker 1>Uh in response, that's right. It just it depends on

0:18:24.680 --> 0:18:29.159
<v Speaker 1>a system of contexts, and without those contexts, and the

0:18:29.160 --> 0:18:32.080
<v Speaker 1>computer has to be able to interpret that well, um,

0:18:32.800 --> 0:18:36.000
<v Speaker 1>you're you know, it's it's not nearly as effective as

0:18:36.040 --> 0:18:39.360
<v Speaker 1>it could be um, So this is this is definitely

0:18:39.359 --> 0:18:41.920
<v Speaker 1>a step in the right direction. Yeah, I think it's

0:18:41.920 --> 0:18:44.679
<v Speaker 1>pretty fascinating the way it talked about how or the

0:18:44.680 --> 0:18:48.240
<v Speaker 1>way the the engineers talked about how the computer comes

0:18:48.320 --> 0:18:50.600
<v Speaker 1>up with its answers. So what it does is it

0:18:50.600 --> 0:18:54.480
<v Speaker 1>will it comes up with candidate answers. This is part

0:18:54.480 --> 0:18:58.159
<v Speaker 1>of that parallel processing where all the potential answers to

0:18:58.200 --> 0:19:01.159
<v Speaker 1>a question pop up, and then it turns each of

0:19:01.200 --> 0:19:06.160
<v Speaker 1>those answers into a hypothesis and then examines each hypothesis

0:19:06.240 --> 0:19:10.399
<v Speaker 1>to determine how likely that hypothesis is in fact the

0:19:10.520 --> 0:19:13.480
<v Speaker 1>right answer, and if it doesn't meet a certain level

0:19:13.560 --> 0:19:18.159
<v Speaker 1>of confidence, then then Watson won't buzz in. So Watson

0:19:18.240 --> 0:19:20.200
<v Speaker 1>is not going to buzz in on every question because

0:19:20.200 --> 0:19:22.119
<v Speaker 1>occasionally there's gonna be a question it's gonna be worded

0:19:22.119 --> 0:19:24.960
<v Speaker 1>in such a way that Watson is not really able

0:19:25.000 --> 0:19:28.520
<v Speaker 1>to interpret what what the answer is or just doesn't

0:19:28.560 --> 0:19:31.120
<v Speaker 1>have the information and database. That's another thing we should

0:19:31.119 --> 0:19:35.000
<v Speaker 1>point out. Watson is completely self contained. Yes, it is

0:19:35.080 --> 0:19:37.480
<v Speaker 1>not hooked up to the Internet, so lest you think

0:19:37.560 --> 0:19:40.119
<v Speaker 1>it is searching on Google, it is not. Right. So

0:19:40.600 --> 0:19:43.520
<v Speaker 1>all the information that Watson has available to it is

0:19:43.720 --> 0:19:47.320
<v Speaker 1>self contained. It doesn't. It cannot get more information during

0:19:47.320 --> 0:19:51.239
<v Speaker 1>the course of a game. Now, in between games, um,

0:19:51.920 --> 0:19:55.160
<v Speaker 1>the people ib folks at IBM where it would update Watson,

0:19:55.359 --> 0:19:58.400
<v Speaker 1>especially with things like pop culture references, so that pop

0:19:58.480 --> 0:20:01.560
<v Speaker 1>so that Watson would be able to interpret questions that

0:20:01.680 --> 0:20:04.000
<v Speaker 1>revolved around pop culture and be able to respond to

0:20:04.040 --> 0:20:06.840
<v Speaker 1>them U or news items, things that just happened in

0:20:06.880 --> 0:20:09.080
<v Speaker 1>the news that would have they'd have to update Watson

0:20:09.119 --> 0:20:11.760
<v Speaker 1>with that information as well. But yeah, the key was

0:20:11.840 --> 0:20:15.640
<v Speaker 1>to be able to let Watson break down a sentence

0:20:15.680 --> 0:20:18.800
<v Speaker 1>and really understand what the sentence was saying, not just

0:20:19.040 --> 0:20:21.640
<v Speaker 1>you know this this must be the object and this

0:20:21.720 --> 0:20:24.560
<v Speaker 1>is the the subject and this is the verb, but

0:20:24.640 --> 0:20:28.360
<v Speaker 1>to really understand what it was saying because uh, context,

0:20:28.400 --> 0:20:30.840
<v Speaker 1>as you were pointing out, is so important. One of

0:20:30.880 --> 0:20:35.760
<v Speaker 1>the elements that they talked about was temporal reasoning. Temporal

0:20:35.840 --> 0:20:39.320
<v Speaker 1>reasoning meaning that, uh, there are different ways of saying

0:20:39.320 --> 0:20:44.359
<v Speaker 1>the same thing. For instance, I could say, uh that, um,

0:20:44.400 --> 0:20:49.320
<v Speaker 1>I graduated twenty years ago, or I could say I graduated,

0:20:51.280 --> 0:20:53.679
<v Speaker 1>or I could say the twenty high school reunion is

0:20:53.720 --> 0:20:56.280
<v Speaker 1>coming up for me. All of those things essentially give

0:20:56.320 --> 0:21:00.120
<v Speaker 1>you the same information. By the way I did not graduate. Um.

0:21:00.160 --> 0:21:03.480
<v Speaker 1>But all that all that information, all those those phrases

0:21:03.480 --> 0:21:08.200
<v Speaker 1>give you the same information that I graduated high school. UM,

0:21:08.200 --> 0:21:10.520
<v Speaker 1>but it's different ways of saying it, and a computer

0:21:10.800 --> 0:21:14.600
<v Speaker 1>does not necessarily know that each of those different sentences

0:21:14.640 --> 0:21:17.080
<v Speaker 1>means the same thing. So they had to find a

0:21:17.119 --> 0:21:21.080
<v Speaker 1>way for Watson to learn that, to learn that there

0:21:21.119 --> 0:21:25.120
<v Speaker 1>are many different ways of conveying the same information using

0:21:25.240 --> 0:21:29.000
<v Speaker 1>totally different sentences. And you'll actually be able to see

0:21:29.000 --> 0:21:32.119
<v Speaker 1>that on on February fourteenth, if you tune in to

0:21:32.160 --> 0:21:35.280
<v Speaker 1>watch the show. That's when it's scheduled to air here

0:21:35.280 --> 0:21:38.320
<v Speaker 1>in the United States. Um. And we we know that,

0:21:38.520 --> 0:21:41.480
<v Speaker 1>we know that it performed pretty well already at least,

0:21:41.680 --> 0:21:44.359
<v Speaker 1>let's kind of get into that. Okay, Sorry, No, I

0:21:44.440 --> 0:21:46.560
<v Speaker 1>just figured after after we you know, we could talk

0:21:46.560 --> 0:21:48.960
<v Speaker 1>about the actual show. It's coming up there. I think

0:21:49.000 --> 0:21:52.280
<v Speaker 1>actually the show itself, uh, this particular episode is going

0:21:52.320 --> 0:21:54.399
<v Speaker 1>to be interesting. But well, I was gonna mention that

0:21:54.440 --> 0:21:59.320
<v Speaker 1>a minute, Okay, uh no, basically one of the things

0:21:59.320 --> 0:22:01.639
<v Speaker 1>that I think is really kind of cool. You're not

0:22:01.680 --> 0:22:04.119
<v Speaker 1>going to be just sitting there watching a box and

0:22:04.200 --> 0:22:07.160
<v Speaker 1>to human opponents, they actually made They actually made an

0:22:07.160 --> 0:22:11.160
<v Speaker 1>interface for people to watch, which I think was probably

0:22:11.200 --> 0:22:14.000
<v Speaker 1>key for Jeopardy because I imagine they would actually want

0:22:14.040 --> 0:22:15.560
<v Speaker 1>to see It's like, well, how do we know what

0:22:15.560 --> 0:22:18.600
<v Speaker 1>it's doing? Um, it could be brewing coffee for all

0:22:18.640 --> 0:22:22.959
<v Speaker 1>we know, um, mr coffee. It has an avatar, then

0:22:23.000 --> 0:22:24.639
<v Speaker 1>you'll see it. It looks kind of like a planet

0:22:24.640 --> 0:22:27.119
<v Speaker 1>with a little uh, I don't know, thought wigglies. What

0:22:27.240 --> 0:22:33.159
<v Speaker 1>do you call those? Illustrated I'd call that Doug's hair. Um. Basically,

0:22:33.400 --> 0:22:36.879
<v Speaker 1>if the computer is feeling I put this in quotes,

0:22:36.920 --> 0:22:39.960
<v Speaker 1>if you don't mind confident, the avatar that you see

0:22:40.040 --> 0:22:43.280
<v Speaker 1>is green, so it has it's feeling pretty sure that

0:22:43.400 --> 0:22:47.160
<v Speaker 1>it's got an answer it can use to to buzz in. However,

0:22:47.240 --> 0:22:50.440
<v Speaker 1>if it doesn't have the correct answer, it will be orange,

0:22:51.160 --> 0:22:53.760
<v Speaker 1>so you will be able to see what's going on,

0:22:53.880 --> 0:22:55.520
<v Speaker 1>and you will also be able to see it thinking

0:22:55.720 --> 0:22:58.800
<v Speaker 1>because as the algorithms are processing information to try to

0:22:58.840 --> 0:23:02.679
<v Speaker 1>find an uh A correct question. It's so weird to

0:23:02.680 --> 0:23:06.080
<v Speaker 1>say in this context, um, the avatar is going to flicker,

0:23:06.240 --> 0:23:08.800
<v Speaker 1>so you'll actually be able to see it in the

0:23:08.840 --> 0:23:12.640
<v Speaker 1>process of trying to determine an answer for itself. Um. Now,

0:23:12.680 --> 0:23:15.320
<v Speaker 1>and in two thousand seven, they started building Watson, which,

0:23:15.320 --> 0:23:18.440
<v Speaker 1>by the way, we didn't mention, I don't think uh uh,

0:23:18.440 --> 0:23:21.160
<v Speaker 1>this is named after IBMS founder Thomas J. Watson nine

0:23:21.160 --> 0:23:26.000
<v Speaker 1>after the h Sir Arthur Arthur Conan Doyle character. Right,

0:23:26.119 --> 0:23:31.440
<v Speaker 1>he's not a doctor who who served in India. Um.

0:23:31.480 --> 0:23:34.439
<v Speaker 1>But yeah, that they actually started working on this problem

0:23:34.520 --> 0:23:37.720
<v Speaker 1>and our project in two thousand seven and didn't really

0:23:37.720 --> 0:23:40.520
<v Speaker 1>have a candidate until that. They were ready to share

0:23:40.520 --> 0:23:44.320
<v Speaker 1>with the Jeopardy producers until late two thousand nine. Now. UM,

0:23:44.359 --> 0:23:46.359
<v Speaker 1>one of the videos, or a couple of videos that

0:23:46.400 --> 0:23:49.879
<v Speaker 1>I saw on the website interviewed one of the producers

0:23:50.119 --> 0:23:53.880
<v Speaker 1>of Jeopardy UM and I had his name, Harry Friedman,

0:23:54.000 --> 0:23:58.320
<v Speaker 1>Executive producer. Uh. And he said, basically, you know, we

0:23:58.320 --> 0:23:59.760
<v Speaker 1>were interested in it, but we didn't want it to

0:23:59.760 --> 0:24:03.240
<v Speaker 1>come off as some kind of stunt. Um. And I

0:24:03.720 --> 0:24:05.880
<v Speaker 1>understand that the Jeopardy has sort of a cache as

0:24:05.920 --> 0:24:08.320
<v Speaker 1>being Uh yes, it's a trivia show. But these people

0:24:08.359 --> 0:24:11.520
<v Speaker 1>are seriously intelligent and they have a lot of domain

0:24:11.680 --> 0:24:15.359
<v Speaker 1>you know, cross domain knowledge. Celebrity Jeopardy accepted, of course,

0:24:16.960 --> 0:24:23.320
<v Speaker 1>we won't go there. Um. Actually some of them are anyway. UM. So,

0:24:23.720 --> 0:24:26.320
<v Speaker 1>but that's always entertaining to there there's an element of entertainment,

0:24:26.359 --> 0:24:30.120
<v Speaker 1>but they also have a certain um cash A yes,

0:24:30.440 --> 0:24:32.879
<v Speaker 1>it's like, yeah, we have seriously smart people on this show.

0:24:32.920 --> 0:24:36.200
<v Speaker 1>We don't we don't want to devolve and cheap in

0:24:36.240 --> 0:24:38.520
<v Speaker 1>the show UM. So they showed it to the producers

0:24:38.520 --> 0:24:40.960
<v Speaker 1>in late two thousand nine, and they have video of

0:24:40.960 --> 0:24:44.720
<v Speaker 1>the producers watching Watson perform in a contest with some

0:24:45.080 --> 0:24:48.639
<v Speaker 1>IBM employees and they seemed pretty impressed. Obviously, they're impressed

0:24:48.720 --> 0:24:50.960
<v Speaker 1>enough to actually go forward with the with the show

0:24:51.960 --> 0:24:55.040
<v Speaker 1>UM now to recruit. They recruited two of the very

0:24:55.080 --> 0:24:59.440
<v Speaker 1>best Jeopardy champions for show UM. You probably have heard

0:24:59.480 --> 0:25:02.720
<v Speaker 1>of both of them. One as Ken Jennings who won

0:25:02.880 --> 0:25:06.480
<v Speaker 1>seventy four games a few years ago one two point

0:25:06.520 --> 0:25:09.000
<v Speaker 1>four million dollars on the show, and Brad Rutter, who

0:25:09.040 --> 0:25:11.560
<v Speaker 1>is the all time money champion who won three million,

0:25:11.600 --> 0:25:16.520
<v Speaker 1>two hundred fifty five thousand, hundred two dollars UM. And

0:25:16.600 --> 0:25:21.000
<v Speaker 1>they stand to win one million dollars. Whomever takes home

0:25:21.080 --> 0:25:23.680
<v Speaker 1>first place will take home a million dollars. Second place

0:25:23.720 --> 0:25:25.960
<v Speaker 1>is good for three hundred thousand dollars, and third is

0:25:26.000 --> 0:25:29.480
<v Speaker 1>to two hundred thousand now that the human contestants I

0:25:29.480 --> 0:25:32.320
<v Speaker 1>have agreed to UH to donate half of that charity,

0:25:32.359 --> 0:25:35.119
<v Speaker 1>and I V will donate all of its prize winnings

0:25:35.119 --> 0:25:37.440
<v Speaker 1>to charity, no matter what place it comes in. Yeah,

0:25:37.480 --> 0:25:40.919
<v Speaker 1>that's pretty phenomenal when you consider how much time and

0:25:41.000 --> 0:25:44.960
<v Speaker 1>effort and money must have been put into this project. Yes, now,

0:25:45.000 --> 0:25:48.040
<v Speaker 1>as Jonathan said, these three have already gone at it

0:25:48.080 --> 0:25:52.639
<v Speaker 1>for a a prep round and Watson did pretty well. Yeah.

0:25:52.800 --> 0:25:54.840
<v Speaker 1>Actually I was doing really really well in the first

0:25:54.840 --> 0:25:59.959
<v Speaker 1>half of the game. It ended up winning. Um. And uh,

0:26:00.000 --> 0:26:02.880
<v Speaker 1>actually they asked Brad Rudder. I read an article in

0:26:02.880 --> 0:26:07.639
<v Speaker 1>in Wired magazine UM by Sam Gustin who who was

0:26:07.680 --> 0:26:10.919
<v Speaker 1>writing who talked to Brad Rudder and said, uh, you

0:26:10.960 --> 0:26:13.439
<v Speaker 1>know that He said, are you scared to be going

0:26:13.520 --> 0:26:16.240
<v Speaker 1>up against his computers? Or nervous? He said, and not

0:26:16.359 --> 0:26:18.840
<v Speaker 1>and this is a quote, not nervous, But I will

0:26:18.880 --> 0:26:21.280
<v Speaker 1>be when Watson's progeny comes back from the future to

0:26:21.359 --> 0:26:24.400
<v Speaker 1>kill me. Yeah. There's been a lot of Skynet jokes

0:26:24.400 --> 0:26:28.000
<v Speaker 1>about this, and how jokes as well. UM, but yeah,

0:26:28.040 --> 0:26:30.320
<v Speaker 1>you know we That's one of the other things that's

0:26:30.320 --> 0:26:33.720
<v Speaker 1>really cool about uh Watson is that you know, I

0:26:33.800 --> 0:26:36.960
<v Speaker 1>mentioned a little bit that it kind of thinks thanks

0:26:37.000 --> 0:26:42.880
<v Speaker 1>being yeah, taken in context, folks. Um, No, that Watson

0:26:43.680 --> 0:26:46.040
<v Speaker 1>looks for answers the same way we do, and that

0:26:46.560 --> 0:26:49.400
<v Speaker 1>it has all this information that's been stored in its database.

0:26:49.440 --> 0:26:51.159
<v Speaker 1>But it's all been stored like in the form of

0:26:51.280 --> 0:26:54.280
<v Speaker 1>books and plays and poems and things like that. Right, Yes,

0:26:54.760 --> 0:26:59.400
<v Speaker 1>So it's not organizing all its information and tables, which

0:26:59.440 --> 0:27:02.080
<v Speaker 1>is typic lee how you would do that in a database,

0:27:02.720 --> 0:27:06.520
<v Speaker 1>you know, it's it's actually searching through contextually, which to

0:27:06.600 --> 0:27:08.520
<v Speaker 1>me is phenomenal. That's one of the reasons why. But

0:27:08.560 --> 0:27:10.639
<v Speaker 1>it's also whether reasons why it does so well because

0:27:10.640 --> 0:27:14.080
<v Speaker 1>it's not looking for specific patterns, it's it's looking through

0:27:14.200 --> 0:27:18.359
<v Speaker 1>the actual information. Um. And it was no small feat

0:27:18.760 --> 0:27:23.240
<v Speaker 1>to design this computer. They had several teams working at IBM.

0:27:23.280 --> 0:27:25.639
<v Speaker 1>Actually I've got I've written down the different teams here

0:27:25.680 --> 0:27:29.720
<v Speaker 1>they had. They had an algorithms team that fifteen people

0:27:29.720 --> 0:27:31.919
<v Speaker 1>on it. By the way, some of these teams had

0:27:32.080 --> 0:27:35.280
<v Speaker 1>just had shared members, like there there would be someone

0:27:35.280 --> 0:27:38.280
<v Speaker 1>who be on more than one team. So in total

0:27:38.320 --> 0:27:40.600
<v Speaker 1>it was around twenty five people who worked on this project,

0:27:41.280 --> 0:27:44.200
<v Speaker 1>but fifteen of them were working on algorithms, and these

0:27:44.200 --> 0:27:47.560
<v Speaker 1>were the ones that would identify the context created by

0:27:47.560 --> 0:27:51.760
<v Speaker 1>the question and and look for the available sources UH

0:27:52.000 --> 0:27:55.760
<v Speaker 1>for answers. UM there was a strategy team, and the

0:27:55.800 --> 0:27:59.920
<v Speaker 1>strategy team actually was in charge of designing Watson's game

0:28:00.080 --> 0:28:04.920
<v Speaker 1>play and betting strategies. Well, that's important, that's um. Yeah again,

0:28:04.960 --> 0:28:07.800
<v Speaker 1>if you haven't watched the show, UH, you know, as

0:28:07.840 --> 0:28:11.119
<v Speaker 1>you go on, you either make money when you answer

0:28:11.240 --> 0:28:14.520
<v Speaker 1>questions correctly, get nothing if you don't answer at all,

0:28:15.600 --> 0:28:17.880
<v Speaker 1>but lose money if you And at the final round,

0:28:17.880 --> 0:28:20.640
<v Speaker 1>there are two rounds of regular questioning and once that's done,

0:28:20.680 --> 0:28:23.960
<v Speaker 1>there's what they call Final jeopardy, which is UH a

0:28:24.119 --> 0:28:28.280
<v Speaker 1>last question on which you are shown the category. So

0:28:28.400 --> 0:28:31.000
<v Speaker 1>you have the domain from which this question is being pulled,

0:28:31.200 --> 0:28:33.760
<v Speaker 1>but you don't know what the answer will be for

0:28:33.840 --> 0:28:35.560
<v Speaker 1>you to come up with a question, so you have

0:28:35.640 --> 0:28:39.120
<v Speaker 1>to bet based on what the other two contestants have

0:28:39.400 --> 0:28:44.160
<v Speaker 1>on on their boards versus what you have earned over

0:28:44.160 --> 0:28:46.400
<v Speaker 1>the course of the game. And if if they both

0:28:46.440 --> 0:28:49.640
<v Speaker 1>have fifteen dollars each then and you have ten thousand,

0:28:49.720 --> 0:28:51.959
<v Speaker 1>then you don't have to worry about your betting strategy. Right.

0:28:52.000 --> 0:28:54.920
<v Speaker 1>If your neck and neck you have to figure out, well,

0:28:55.000 --> 0:28:58.240
<v Speaker 1>do I know enough to answer this question or question

0:28:58.320 --> 0:29:01.160
<v Speaker 1>this answer it really is? Or do I do I

0:29:01.360 --> 0:29:04.160
<v Speaker 1>wager that they don't know what it is, and therefore

0:29:04.200 --> 0:29:07.000
<v Speaker 1>I keep my bets small, hoping that they're going to

0:29:07.080 --> 0:29:10.080
<v Speaker 1>bet big and lose enough money so that I win anyway?

0:29:10.200 --> 0:29:12.560
<v Speaker 1>Or am I in the lead? Do I? Am I

0:29:12.560 --> 0:29:14.680
<v Speaker 1>in the lead enough where I can bet a smaller

0:29:14.720 --> 0:29:17.520
<v Speaker 1>amount just so that in case either of them double up,

0:29:17.520 --> 0:29:20.480
<v Speaker 1>they still don't overtake me. Yeah, there's a lot of

0:29:20.480 --> 0:29:23.720
<v Speaker 1>betting strategy involved. Or you could cliff clayvin it and

0:29:23.800 --> 0:29:26.480
<v Speaker 1>just bet the whole thing, even though you are hopelessly

0:29:26.720 --> 0:29:28.440
<v Speaker 1>in the lead. I mean, there's like no way you

0:29:28.440 --> 0:29:30.800
<v Speaker 1>could lose. You bet the whole thing and then you lose.

0:29:31.720 --> 0:29:36.080
<v Speaker 1>Who are seven people who have never been in my kitchen? Uh?

0:29:36.080 --> 0:29:37.960
<v Speaker 1>So Yeah, the strategy team, they were in charge of

0:29:38.440 --> 0:29:42.120
<v Speaker 1>the game playing betting strategies. Then you had the systems team,

0:29:42.240 --> 0:29:46.560
<v Speaker 1>um and uh they were the ones who helped design

0:29:46.640 --> 0:29:49.600
<v Speaker 1>the way that Watson would interpret a question across thousands

0:29:49.640 --> 0:29:52.920
<v Speaker 1>of different cores, you know. So then you've got the

0:29:52.920 --> 0:29:55.040
<v Speaker 1>speech team. So that's the team that actually worked on

0:29:55.080 --> 0:29:58.120
<v Speaker 1>that text to speech capability so that Watson talks too.

0:29:58.600 --> 0:30:00.840
<v Speaker 1>In the game. You don't just see words appear on

0:30:00.840 --> 0:30:03.680
<v Speaker 1>the screen. Watson actually has a voice. It does not

0:30:03.760 --> 0:30:06.640
<v Speaker 1>always pronounce everything correctly, but they worked very hard to

0:30:06.680 --> 0:30:10.240
<v Speaker 1>try and give him a pretty wide range of pronunciations

0:30:10.240 --> 0:30:14.360
<v Speaker 1>because Jeopardy tends to use lots of fancy words. Um.

0:30:14.480 --> 0:30:17.880
<v Speaker 1>There was an annotations team which built the taxonomy for

0:30:17.960 --> 0:30:23.480
<v Speaker 1>the search databases. That's interesting to all our librarians out there. Yes,

0:30:23.680 --> 0:30:26.720
<v Speaker 1>taxonomies are important. I mean, that's how you find information,

0:30:26.720 --> 0:30:28.120
<v Speaker 1>and of course you have to design in such a

0:30:28.160 --> 0:30:30.520
<v Speaker 1>way so that the computer can hit the most likely

0:30:30.560 --> 0:30:33.000
<v Speaker 1>sources first so you can come up with the answer

0:30:33.040 --> 0:30:36.760
<v Speaker 1>as quickly as possible. Uh. There are also teams in China,

0:30:36.880 --> 0:30:40.960
<v Speaker 1>Tokyo and Haifa. Uh. There was a project management team

0:30:41.040 --> 0:30:44.240
<v Speaker 1>which was sort of the liaison between Jeopardy and IBM.

0:30:44.320 --> 0:30:46.760
<v Speaker 1>And then there was an applications team, and that's the

0:30:46.800 --> 0:30:50.240
<v Speaker 1>one that I think is really the most interesting moving forward,

0:30:50.280 --> 0:30:53.640
<v Speaker 1>no matter whether Watson wins on the fourteenth or not.

0:30:54.840 --> 0:30:57.800
<v Speaker 1>The applications team, that's the group that's looking at ways

0:30:57.880 --> 0:31:01.760
<v Speaker 1>to use this kind of capability. Be yawned. The Jeopardy

0:31:01.840 --> 0:31:06.360
<v Speaker 1>scenario so some of the examples I heard were included,

0:31:06.400 --> 0:31:08.440
<v Speaker 1>Like the one that they spent the most time on

0:31:08.560 --> 0:31:13.600
<v Speaker 1>was a diagnostics like medical diagnoses. Yeah, the idea being

0:31:13.640 --> 0:31:18.360
<v Speaker 1>that you could input your doctors could use this when

0:31:18.640 --> 0:31:23.280
<v Speaker 1>seeing patients who are giving, you know, interesting symptoms, something

0:31:23.280 --> 0:31:26.840
<v Speaker 1>that maybe was contradictory, and you would use a computer

0:31:26.960 --> 0:31:32.280
<v Speaker 1>that could could essentially reference the world's information on medical

0:31:32.720 --> 0:31:37.760
<v Speaker 1>knowledge and come up with the most likely of diagnoses,

0:31:38.240 --> 0:31:42.240
<v Speaker 1>which is pretty interesting. But I've also seen other potential

0:31:42.320 --> 0:31:44.960
<v Speaker 1>uses of government and law were two that were mentioned

0:31:45.000 --> 0:31:46.640
<v Speaker 1>as well, which is kind of interesting where you know,

0:31:46.680 --> 0:31:49.880
<v Speaker 1>you start looking for a precedent maybe for a law

0:31:49.920 --> 0:31:54.520
<v Speaker 1>case or something along those lines. So, um, yeah, there's

0:31:54.560 --> 0:31:59.240
<v Speaker 1>there's definitely uses for this beyond just hitting that daily double.

0:32:00.080 --> 0:32:02.760
<v Speaker 1>That's true. That's true. You know, I was just thinking

0:32:02.760 --> 0:32:05.960
<v Speaker 1>about it, uh too. I was reversing in my head

0:32:06.000 --> 0:32:09.920
<v Speaker 1>the betting strategy because when you when you mentioned whether

0:32:10.600 --> 0:32:13.600
<v Speaker 1>Watson wins or not, I started thinking, what if you're

0:32:14.040 --> 0:32:17.000
<v Speaker 1>Brad Rutter or Ken Jennings and you're trying to devise

0:32:17.040 --> 0:32:19.440
<v Speaker 1>a betting strategy and you're like, well, I know he's

0:32:19.480 --> 0:32:21.840
<v Speaker 1>going to do this because I've seen him. I mean,

0:32:21.840 --> 0:32:24.240
<v Speaker 1>both of these guys have played Jeopardy enough times where

0:32:24.240 --> 0:32:27.400
<v Speaker 1>the other one probably knows how they're going to bet.

0:32:27.840 --> 0:32:31.440
<v Speaker 1>But how do you devise a betting strategy against the computer,

0:32:31.760 --> 0:32:34.200
<v Speaker 1>especially a computer that seems to jump all over the board.

0:32:34.480 --> 0:32:36.719
<v Speaker 1>Did you watch any of the things where like there

0:32:36.800 --> 0:32:39.880
<v Speaker 1>was one there was one video in particular where Watson

0:32:39.920 --> 0:32:42.040
<v Speaker 1>got someone went went for like one of the two

0:32:42.120 --> 0:32:45.480
<v Speaker 1>hundred dollar questions, which is the lowest level, right right,

0:32:45.800 --> 0:32:48.000
<v Speaker 1>and uh, and Watson got it right. And then Watson

0:32:48.000 --> 0:32:51.440
<v Speaker 1>went immediately for the thousand or two thousand whatever the

0:32:51.440 --> 0:32:53.640
<v Speaker 1>top level question is now on on that board, it's

0:32:53.680 --> 0:32:56.000
<v Speaker 1>a thousand, okay, So he went right for the like

0:32:56.760 --> 0:32:59.400
<v Speaker 1>in the category had been untouched, so all of the

0:32:59.640 --> 0:33:04.520
<v Speaker 1>all of the versions were available, every single variation of

0:33:04.800 --> 0:33:07.200
<v Speaker 1>however much. I can't even remember how they go anymore

0:33:07.200 --> 0:33:09.640
<v Speaker 1>because I haven't watched it so long. The first round

0:33:09.680 --> 0:33:12.080
<v Speaker 1>of Jeopardy is two hundred four six eight hundred and

0:33:12.120 --> 0:33:14.120
<v Speaker 1>a thousand dollar questions for each kid right, and then

0:33:14.200 --> 0:33:17.400
<v Speaker 1>it doubles four. And I remember when it was one

0:33:17.760 --> 0:33:21.440
<v Speaker 1>d two or three hundred four and oh my god,

0:33:21.160 --> 0:33:24.280
<v Speaker 1>we're old. I think there are people who remember when

0:33:24.280 --> 0:33:32.640
<v Speaker 1>it was um, yeah, Serony San Francisco treat. Uh, I'm

0:33:32.680 --> 0:33:34.880
<v Speaker 1>sorry that was that was I lost on Jeopardy by

0:33:35.000 --> 0:33:37.800
<v Speaker 1>weird al Yankovic. I remember that too. Yeah, I also

0:33:37.960 --> 0:33:40.960
<v Speaker 1>remember when that came out on three D. I think

0:33:41.920 --> 0:33:44.880
<v Speaker 1>I think this is gonna be a fun exper I'm

0:33:44.880 --> 0:33:46.560
<v Speaker 1>sure it's It's been fun for the people who've been

0:33:46.560 --> 0:33:50.120
<v Speaker 1>working on and extremely challenging. Um. I'm interested to see

0:33:50.120 --> 0:33:53.400
<v Speaker 1>how it turns out and whether or not IBM will

0:33:53.440 --> 0:33:55.920
<v Speaker 1>be up for a rematch. Depending on how it goes,

0:33:55.960 --> 0:33:58.400
<v Speaker 1>will they be able to improve it enough, and will

0:33:58.440 --> 0:34:00.720
<v Speaker 1>they convinced the Jeopardy producers to them back on. But

0:34:00.960 --> 0:34:03.120
<v Speaker 1>I think it's gonna be fun. It'll be fun to watch, yeah,

0:34:03.160 --> 0:34:07.160
<v Speaker 1>even if even if it loses. It's such a phenomenal

0:34:07.320 --> 0:34:12.520
<v Speaker 1>achievement to create the algorithms and the database necessary to

0:34:12.560 --> 0:34:15.720
<v Speaker 1>be able to navigate natural language. I mean, that really

0:34:15.880 --> 0:34:20.760
<v Speaker 1>is I did not expect to see it this early,

0:34:21.360 --> 0:34:23.560
<v Speaker 1>you know, I thought that might be a thing, not

0:34:23.680 --> 0:34:27.400
<v Speaker 1>a not a twenty eleven thing. It's it's extremely difficult

0:34:27.440 --> 0:34:30.719
<v Speaker 1>to do. As you can the aforementioned librarians will tell

0:34:30.760 --> 0:34:35.720
<v Speaker 1>you or the catalogs to process natural language questions English English,

0:34:35.800 --> 0:34:38.360
<v Speaker 1>majors will tell you that the language is very difficult

0:34:38.360 --> 0:34:41.840
<v Speaker 1>as well. And you know, so my hat is off

0:34:41.880 --> 0:34:46.040
<v Speaker 1>to to IBM and those those engineers and employees who

0:34:46.120 --> 0:34:49.520
<v Speaker 1>all work together to bring this this technology to life

0:34:49.520 --> 0:34:53.359
<v Speaker 1>because um, like you know, even the applications they were

0:34:53.400 --> 0:34:57.160
<v Speaker 1>talking about, that's just the beginning. We had talked about

0:34:57.160 --> 0:35:00.839
<v Speaker 1>the semantic web before. Um, this is really kind of

0:35:00.880 --> 0:35:04.239
<v Speaker 1>what the semantic web is promising, is as this this

0:35:04.400 --> 0:35:07.640
<v Speaker 1>web experience, uh not grant again. Watson is not a

0:35:07.680 --> 0:35:09.879
<v Speaker 1>web based experience, but a web experience where it can

0:35:09.960 --> 0:35:14.319
<v Speaker 1>understand what you're saying and give you the right response. Oh, yeah,

0:35:14.360 --> 0:35:17.359
<v Speaker 1>I know what you mean. You're looking for this right, right? Yeah, like,

0:35:17.520 --> 0:35:19.920
<v Speaker 1>and I mean it's amazing. You could think in a

0:35:19.960 --> 0:35:21.920
<v Speaker 1>few years you could have a computer that can understand

0:35:21.920 --> 0:35:26.360
<v Speaker 1>a joke. Supposedly it made a joke and yeah. And

0:35:26.560 --> 0:35:31.000
<v Speaker 1>when one of the preliminary games, supposedly it said something

0:35:31.040 --> 0:35:33.600
<v Speaker 1>that caused the entire audience to laugh, and it was

0:35:34.000 --> 0:35:35.680
<v Speaker 1>that it was I think it was Fox News that

0:35:35.719 --> 0:35:38.440
<v Speaker 1>was reporting it, and they did not go into detail

0:35:38.520 --> 0:35:41.680
<v Speaker 1>about what this thing was, but they said that it

0:35:41.800 --> 0:35:43.600
<v Speaker 1>was at the end of one of the like Watson

0:35:43.640 --> 0:35:48.399
<v Speaker 1>got something right and then said something that made people laugh. Now,

0:35:48.400 --> 0:35:50.280
<v Speaker 1>whether or not it was a joke in the sense

0:35:50.360 --> 0:35:55.279
<v Speaker 1>that the computers somehow manifested this desire to make a joke,

0:35:55.400 --> 0:35:57.959
<v Speaker 1>I don't know, because clearly we're not talking about saying

0:35:58.000 --> 0:36:02.040
<v Speaker 1>that's actually alive. If answer is correct and next next

0:36:02.120 --> 0:36:08.640
<v Speaker 1>question has not been asked, say yeah, people on that show, um,

0:36:08.680 --> 0:36:11.640
<v Speaker 1>just follow that logic. So and I'm also looking forward

0:36:11.640 --> 0:36:14.080
<v Speaker 1>to the segment before the second round begins where they

0:36:14.080 --> 0:36:16.640
<v Speaker 1>start asking you about your background. Right, well, Alex, I

0:36:16.680 --> 0:36:18.560
<v Speaker 1>was born four years ago. Right, Well, I don't know

0:36:18.560 --> 0:36:21.640
<v Speaker 1>if you could say born right, And I like computing,

0:36:21.800 --> 0:36:24.279
<v Speaker 1>reading and long walks on the beach. But yeah, the

0:36:24.280 --> 0:36:26.160
<v Speaker 1>other the other side of this that we haven't really

0:36:26.200 --> 0:36:28.080
<v Speaker 1>touched on, and I think it's a good place to

0:36:28.080 --> 0:36:32.200
<v Speaker 1>wrap up. It really shows you how remarkable human beings are. Yeah,

0:36:32.800 --> 0:36:35.440
<v Speaker 1>because look at what has to happen. In order for

0:36:35.520 --> 0:36:38.440
<v Speaker 1>a machine to compete against humans. You have to have

0:36:39.440 --> 0:36:43.440
<v Speaker 1>two thousand, eight h eight cores processors, you have to

0:36:43.480 --> 0:36:46.799
<v Speaker 1>have fifteen terabytes of RAM. You have to have this

0:36:47.080 --> 0:36:50.399
<v Speaker 1>computer that has the equivalent of two million books worth

0:36:50.440 --> 0:36:54.319
<v Speaker 1>of information stored on it. In order to compete with

0:36:54.920 --> 0:36:58.600
<v Speaker 1>humans and in order to even come close right too,

0:36:58.640 --> 0:37:01.160
<v Speaker 1>I mean if if it doesn't win. So that's really

0:37:01.280 --> 0:37:04.759
<v Speaker 1>kind of a testament to how amazing people are, not

0:37:04.800 --> 0:37:08.240
<v Speaker 1>just how amazing the technology is. And I I also

0:37:08.400 --> 0:37:12.000
<v Speaker 1>think it's nice that IBM found a way to do

0:37:12.040 --> 0:37:15.319
<v Speaker 1>this experiment in a way that will actually make people interested,

0:37:15.920 --> 0:37:18.000
<v Speaker 1>right and it building some interesting and I'm glad that

0:37:18.000 --> 0:37:22.440
<v Speaker 1>that Sony Uh Entertainment has found a way to uh,

0:37:22.480 --> 0:37:26.879
<v Speaker 1>you know, use this to their advantage to to show off, um,

0:37:26.920 --> 0:37:29.839
<v Speaker 1>you know, how cool they are essentially, you know, and

0:37:29.840 --> 0:37:33.560
<v Speaker 1>and give IBM an opportunity to play. It's definitely a nice,

0:37:33.920 --> 0:37:37.200
<v Speaker 1>a nice uh event to see. I mean the fact

0:37:37.239 --> 0:37:41.200
<v Speaker 1>that it's going to promote this idea of of the

0:37:41.239 --> 0:37:45.920
<v Speaker 1>semantic computing and artificial intelligence in a way that is

0:37:46.280 --> 0:37:50.680
<v Speaker 1>both entertaining and and really informative. It's it was clever.

0:37:50.719 --> 0:37:55.960
<v Speaker 1>It's a very clever approach. Definitely, So kudos IBM, kudos Jeopardy.

0:37:56.760 --> 0:38:00.160
<v Speaker 1>And with that we're going to wrap this up. You

0:38:00.280 --> 0:38:03.520
<v Speaker 1>have any suggestions for topics or you want to chime

0:38:03.560 --> 0:38:06.520
<v Speaker 1>in on our discussion about Watson, you can let us

0:38:06.520 --> 0:38:09.319
<v Speaker 1>know on Twitter or Facebook. Are handled. There is tech

0:38:09.400 --> 0:38:12.600
<v Speaker 1>stuff hs W or you can write us an email

0:38:12.640 --> 0:38:16.000
<v Speaker 1>and that address is tech stuff at how stuff works

0:38:16.000 --> 0:38:17.760
<v Speaker 1>dot com and Chris and I will talt you again

0:38:18.680 --> 0:38:24.160
<v Speaker 1>really soon. Boop For more on this and thousands of

0:38:24.200 --> 0:38:26.640
<v Speaker 1>other topics. Is it how stuff works dot com. So

0:38:26.760 --> 0:38:29.600
<v Speaker 1>learn more about the podcast clock on the podcast icon

0:38:29.719 --> 0:38:32.920
<v Speaker 1>in the upper right corner of our homepage. The How

0:38:33.000 --> 0:38:36.719
<v Speaker 1>Stuff Works iPhone app has arrived. Download it today on iTunes,

0:38:41.600 --> 0:38:44.200
<v Speaker 1>brought to you by the reinvented two thousand twelve camera.

0:38:44.480 --> 0:38:45.719
<v Speaker 1>It's ready. Are you