WEBVTT Kind: captions Language: en 00:00:02.470 --> 00:00:07.750 align:start position:0% [Music] 00:00:07.750 --> 00:00:07.760 align:start position:0% 00:00:07.760 --> 00:00:10.400 align:start position:0% hello<00:00:08.760> everybody<00:00:08.940> I'm<00:00:09.420> Alexey<00:00:09.809> Krylov<00:00:09.960> the 00:00:10.400 --> 00:00:10.410 align:start position:0% hello everybody I'm Alexey Krylov the 00:00:10.410 --> 00:00:13.160 align:start position:0% hello everybody I'm Alexey Krylov the father<00:00:10.679> an<00:00:10.889> organizer<00:00:11.400> of<00:00:11.610> by<00:00:11.880> Eric<00:00:12.300> this<00:00:13.049> is 00:00:13.160 --> 00:00:13.170 align:start position:0% father an organizer of by Eric this is 00:00:13.170 --> 00:00:15.499 align:start position:0% father an organizer of by Eric this is our<00:00:13.290> first<00:00:13.530> meetup<00:00:13.980> of<00:00:14.219> 2019<00:00:14.849> we're<00:00:15.150> here<00:00:15.389> on 00:00:15.499 --> 00:00:15.509 align:start position:0% our first meetup of 2019 we're here on 00:00:15.509 --> 00:00:18.140 align:start position:0% our first meetup of 2019 we're here on location<00:00:15.540> on<00:00:15.929> Domino<00:00:16.350> data<00:00:16.500> labs<00:00:16.890> which<00:00:17.880> we've 00:00:18.140 --> 00:00:18.150 align:start position:0% location on Domino data labs which we've 00:00:18.150 --> 00:00:19.849 align:start position:0% location on Domino data labs which we've seen<00:00:18.390> grow<00:00:18.720> from<00:00:18.930> a<00:00:19.020> few<00:00:19.170> people<00:00:19.470> at<00:00:19.560> galvanize 00:00:19.849 --> 00:00:19.859 align:start position:0% seen grow from a few people at galvanize 00:00:19.859 --> 00:00:23.359 align:start position:0% seen grow from a few people at galvanize the<00:00:20.369> big<00:00:20.609> company<00:00:21.029> now<00:00:21.529> they<00:00:22.529> use<00:00:22.680> Cullen<00:00:23.130> the 00:00:23.359 --> 00:00:23.369 align:start position:0% the big company now they use Cullen the 00:00:23.369 --> 00:00:25.700 align:start position:0% the big company now they use Cullen the backhand<00:00:23.789> and<00:00:24.449> the<00:00:24.510> serve<00:00:24.810> data<00:00:25.109> scientists 00:00:25.700 --> 00:00:25.710 align:start position:0% backhand and the serve data scientists 00:00:25.710 --> 00:00:28.700 align:start position:0% backhand and the serve data scientists in<00:00:26.580> the<00:00:26.760> cloud<00:00:27.000> and<00:00:27.840> so<00:00:28.050> we're<00:00:28.289> happy<00:00:28.470> to<00:00:28.590> be 00:00:28.700 --> 00:00:28.710 align:start position:0% in the cloud and so we're happy to be 00:00:28.710 --> 00:00:31.700 align:start position:0% in the cloud and so we're happy to be here<00:00:28.740> on<00:00:28.980> location<00:00:29.099> our<00:00:29.789> first<00:00:30.630> speaker<00:00:31.230> is<00:00:31.619> a 00:00:31.700 --> 00:00:31.710 align:start position:0% here on location our first speaker is a 00:00:31.710 --> 00:00:33.650 align:start position:0% here on location our first speaker is a moral<00:00:32.009> Lanza<00:00:32.399> whose<00:00:32.910> principal<00:00:33.360> software 00:00:33.650 --> 00:00:33.660 align:start position:0% moral Lanza whose principal software 00:00:33.660 --> 00:00:36.979 align:start position:0% moral Lanza whose principal software engineer<00:00:34.079> at<00:00:34.380> Microsoft<00:00:34.530> and<00:00:35.430> he<00:00:36.420> is<00:00:36.930> a 00:00:36.979 --> 00:00:36.989 align:start position:0% engineer at Microsoft and he is a 00:00:36.989 --> 00:00:39.200 align:start position:0% engineer at Microsoft and he is a veteran<00:00:37.290> by<00:00:38.040> the<00:00:38.100> bands<00:00:38.550> he<00:00:38.879> talked<00:00:39.120> about 00:00:39.200 --> 00:00:39.210 align:start position:0% veteran by the bands he talked about 00:00:39.210 --> 00:00:45.139 align:start position:0% veteran by the bands he talked about data<00:00:39.809> data<00:00:40.410> by<00:00:40.620> the<00:00:40.680> bay<00:00:41.780> before<00:00:42.780> and<00:00:43.200> so<00:00:44.149> we're 00:00:45.139 --> 00:00:45.149 align:start position:0% data data by the bay before and so we're 00:00:45.149 --> 00:00:46.549 align:start position:0% data data by the bay before and so we're very<00:00:45.300> happy<00:00:45.420> to<00:00:45.600> have<00:00:45.719> it<00:00:45.750> here<00:00:45.840> thank<00:00:46.500> you 00:00:46.549 --> 00:00:46.559 align:start position:0% very happy to have it here thank you 00:00:46.559 --> 00:00:48.709 align:start position:0% very happy to have it here thank you very<00:00:46.649> much<00:00:46.920> romantic<00:00:47.610> saying<00:00:47.820> so<00:00:48.300> can<00:00:48.660> you 00:00:48.709 --> 00:00:48.719 align:start position:0% very much romantic saying so can you 00:00:48.719 --> 00:00:50.770 align:start position:0% very much romantic saying so can you tell<00:00:48.870> us<00:00:48.930> a<00:00:49.020> little<00:00:49.079> bit<00:00:49.410> if<00:00:49.770> you<00:00:49.800> know 00:00:50.770 --> 00:00:50.780 align:start position:0% tell us a little bit if you know 00:00:50.780 --> 00:00:54.049 align:start position:0% tell us a little bit if you know basically<00:00:51.780> what<00:00:51.930> your<00:00:52.110> focuses<00:00:52.739> and<00:00:53.219> what 00:00:54.049 --> 00:00:54.059 align:start position:0% basically what your focuses and what 00:00:54.059 --> 00:00:55.369 align:start position:0% basically what your focuses and what have<00:00:54.300> you<00:00:54.390> been<00:00:54.510> doing<00:00:54.780> for<00:00:54.960> last<00:00:55.170> couple 00:00:55.369 --> 00:00:55.379 align:start position:0% have you been doing for last couple 00:00:55.379 --> 00:00:55.760 align:start position:0% have you been doing for last couple years 00:00:55.760 --> 00:00:55.770 align:start position:0% years 00:00:55.770 --> 00:00:58.430 align:start position:0% years sure<00:00:56.460> so<00:00:56.760> my<00:00:56.969> interest<00:00:57.660> is<00:00:57.809> mostly<00:00:58.140> on<00:00:58.289> the 00:00:58.430 --> 00:00:58.440 align:start position:0% sure so my interest is mostly on the 00:00:58.440 --> 00:01:00.229 align:start position:0% sure so my interest is mostly on the intersection<00:00:59.160> of<00:00:59.280> information<00:00:59.879> retrieval 00:01:00.229 --> 00:01:00.239 align:start position:0% intersection of information retrieval 00:01:00.239 --> 00:01:02.229 align:start position:0% intersection of information retrieval knowledge<00:01:00.750> graphs<00:01:00.989> and<00:01:01.289> human<00:01:01.680> computation 00:01:02.229 --> 00:01:02.239 align:start position:0% knowledge graphs and human computation 00:01:02.239 --> 00:01:05.240 align:start position:0% knowledge graphs and human computation and<00:01:03.239> we<00:01:03.300> were<00:01:04.170> working<00:01:04.409> obviously<00:01:04.920> with<00:01:05.100> a<00:01:05.129> lot 00:01:05.240 --> 00:01:05.250 align:start position:0% and we were working obviously with a lot 00:01:05.250 --> 00:01:07.310 align:start position:0% and we were working obviously with a lot of<00:01:05.280> social<00:01:05.549> data<00:01:05.880> in<00:01:06.479> the<00:01:06.810> last<00:01:07.020> two<00:01:07.290> years 00:01:07.310 --> 00:01:07.320 align:start position:0% of social data in the last two years 00:01:07.320 --> 00:01:08.840 align:start position:0% of social data in the last two years we've<00:01:08.100> been<00:01:08.250> doing<00:01:08.460> a<00:01:08.490> lot<00:01:08.610> of<00:01:08.640> knowledge 00:01:08.840 --> 00:01:08.850 align:start position:0% we've been doing a lot of knowledge 00:01:08.850 --> 00:01:10.700 align:start position:0% we've been doing a lot of knowledge graph<00:01:09.180> extraction<00:01:09.720> from<00:01:09.960> different<00:01:10.320> sources 00:01:10.700 --> 00:01:10.710 align:start position:0% graph extraction from different sources 00:01:10.710 --> 00:01:13.160 align:start position:0% graph extraction from different sources not<00:01:11.610> only<00:01:11.760> Twitter<00:01:12.090> what<00:01:12.840> also<00:01:12.960> other 00:01:13.160 --> 00:01:13.170 align:start position:0% not only Twitter what also other 00:01:13.170 --> 00:01:16.190 align:start position:0% not only Twitter what also other Microsoft<00:01:13.740> data<00:01:14.130> sources<00:01:14.460> the<00:01:15.450> talk<00:01:15.630> today<00:01:15.780> is 00:01:16.190 --> 00:01:16.200 align:start position:0% Microsoft data sources the talk today is 00:01:16.200 --> 00:01:18.200 align:start position:0% Microsoft data sources the talk today is one<00:01:16.710> of<00:01:16.740> those<00:01:16.920> projects<00:01:17.340> but<00:01:17.790> it's<00:01:17.909> basically 00:01:18.200 --> 00:01:18.210 align:start position:0% one of those projects but it's basically 00:01:18.210 --> 00:01:21.230 align:start position:0% one of those projects but it's basically mainly<00:01:18.659> about<00:01:19.640> unsupervised<00:01:20.640> generation<00:01:21.119> of 00:01:21.230 --> 00:01:21.240 align:start position:0% mainly about unsupervised generation of 00:01:21.240 --> 00:01:23.899 align:start position:0% mainly about unsupervised generation of knowledge<00:01:21.450> graphs<00:01:21.720> mmm<00:01:22.439> so<00:01:22.890> are<00:01:23.280> you<00:01:23.580> I<00:01:23.610> think 00:01:23.899 --> 00:01:23.909 align:start position:0% knowledge graphs mmm so are you I think 00:01:23.909 --> 00:01:26.600 align:start position:0% knowledge graphs mmm so are you I think you<00:01:24.450> can't<00:01:24.689> given<00:01:25.530> talks<00:01:25.890> about<00:01:26.159> label 00:01:26.600 --> 00:01:26.610 align:start position:0% you can't given talks about label 00:01:26.610 --> 00:01:29.870 align:start position:0% you can't given talks about label quality<00:01:27.350> at<00:01:28.350> our<00:01:28.590> previous<00:01:29.220> event<00:01:29.430> and<00:01:29.640> I 00:01:29.870 --> 00:01:29.880 align:start position:0% quality at our previous event and I 00:01:29.880 --> 00:01:31.700 align:start position:0% quality at our previous event and I think<00:01:30.060> that<00:01:30.180> was<00:01:30.329> one<00:01:30.509> of<00:01:30.689> the<00:01:30.869> really 00:01:31.700 --> 00:01:31.710 align:start position:0% think that was one of the really 00:01:31.710 --> 00:01:33.950 align:start position:0% think that was one of the really foundational<00:01:32.040> topics<00:01:32.340> so<00:01:33.270> I'm<00:01:33.360> curious<00:01:33.810> how 00:01:33.950 --> 00:01:33.960 align:start position:0% foundational topics so I'm curious how 00:01:33.960 --> 00:01:36.920 align:start position:0% foundational topics so I'm curious how did<00:01:34.170> you<00:01:34.290> come<00:01:34.500> to<00:01:34.530> the<00:01:34.770> area<00:01:35.520> you<00:01:36.360> know<00:01:36.509> like 00:01:36.920 --> 00:01:36.930 align:start position:0% did you come to the area you know like 00:01:36.930 --> 00:01:39.200 align:start position:0% did you come to the area you know like what<00:01:37.380> what<00:01:37.860> is<00:01:37.979> it<00:01:38.070> about<00:01:38.159> data<00:01:38.490> quality<00:01:39.030> we 00:01:39.200 --> 00:01:39.210 align:start position:0% what what is it about data quality we 00:01:39.210 --> 00:01:41.569 align:start position:0% what what is it about data quality we should<00:01:39.479> talk<00:01:39.659> to<00:01:39.689> you<00:01:40.020> one<00:01:40.890> of<00:01:40.920> the<00:01:41.009> reasons<00:01:41.070> is 00:01:41.569 --> 00:01:41.579 align:start position:0% should talk to you one of the reasons is 00:01:41.579 --> 00:01:43.880 align:start position:0% should talk to you one of the reasons is if<00:01:42.060> you<00:01:42.240> want<00:01:42.450> to<00:01:42.570> play<00:01:42.930> with<00:01:43.140> new<00:01:43.320> data<00:01:43.590> sets 00:01:43.880 --> 00:01:43.890 align:start position:0% if you want to play with new data sets 00:01:43.890 --> 00:01:45.679 align:start position:0% if you want to play with new data sets like<00:01:44.280> information<00:01:44.610> retrieval<00:01:45.210> and<00:01:45.329> you<00:01:45.570> want 00:01:45.679 --> 00:01:45.689 align:start position:0% like information retrieval and you want 00:01:45.689 --> 00:01:47.420 align:start position:0% like information retrieval and you want to<00:01:45.750> work<00:01:45.840> on<00:01:45.960> search<00:01:46.259> at<00:01:46.619> some<00:01:47.040> point<00:01:47.220> you<00:01:47.310> have 00:01:47.420 --> 00:01:47.430 align:start position:0% to work on search at some point you have 00:01:47.430 --> 00:01:49.520 align:start position:0% to work on search at some point you have to<00:01:47.460> do<00:01:47.610> evaluation<00:01:48.240> and<00:01:48.960> if<00:01:49.110> you<00:01:49.200> don't<00:01:49.380> have 00:01:49.520 --> 00:01:49.530 align:start position:0% to do evaluation and if you don't have 00:01:49.530 --> 00:01:51.499 align:start position:0% to do evaluation and if you don't have ground<00:01:49.860> truth<00:01:50.100> it's<00:01:50.399> very<00:01:50.520> difficult<00:01:51.270> to 00:01:51.499 --> 00:01:51.509 align:start position:0% ground truth it's very difficult to 00:01:51.509 --> 00:01:54.469 align:start position:0% ground truth it's very difficult to build<00:01:52.170> those<00:01:52.409> data<00:01:52.680> sets<00:01:52.950> and<00:01:53.189> when<00:01:54.119> I<00:01:54.149> was<00:01:54.329> at 00:01:54.469 --> 00:01:54.479 align:start position:0% build those data sets and when I was at 00:01:54.479 --> 00:01:56.539 align:start position:0% build those data sets and when I was at a<00:01:54.509> nine<00:01:54.810> I<00:01:55.229> you<00:01:55.710> know<00:01:55.829> learn<00:01:56.009> Mechanical<00:01:56.520> Turk 00:01:56.539 --> 00:01:56.549 align:start position:0% a nine I you know learn Mechanical Turk 00:01:56.549 --> 00:01:59.120 align:start position:0% a nine I you know learn Mechanical Turk and<00:01:57.030> I<00:01:57.360> got<00:01:57.659> hooked<00:01:57.840> into<00:01:58.079> the<00:01:58.259> idea<00:01:58.469> of<00:01:58.799> doing 00:01:59.120 --> 00:01:59.130 align:start position:0% and I got hooked into the idea of doing 00:01:59.130 --> 00:02:02.090 align:start position:0% and I got hooked into the idea of doing labeling<00:01:59.610> in<00:02:00.119> general<00:02:00.479> that's<00:02:01.290> how<00:02:01.409> I<00:02:01.469> got<00:02:02.040> to 00:02:02.090 --> 00:02:02.100 align:start position:0% labeling in general that's how I got to 00:02:02.100 --> 00:02:03.980 align:start position:0% labeling in general that's how I got to do<00:02:02.369> labeling<00:02:02.820> that's<00:02:03.000> how<00:02:03.180> by<00:02:03.450> the<00:02:03.509> way<00:02:03.719> I<00:02:03.750> gave 00:02:03.980 --> 00:02:03.990 align:start position:0% do labeling that's how by the way I gave 00:02:03.990 --> 00:02:06.980 align:start position:0% do labeling that's how by the way I gave the<00:02:04.380> talk<00:02:04.619> and<00:02:04.979> thanks<00:02:05.490> to<00:02:05.640> you<00:02:05.820> but<00:02:06.119> I'm 00:02:06.980 --> 00:02:06.990 align:start position:0% the talk and thanks to you but I'm 00:02:06.990 --> 00:02:09.919 align:start position:0% the talk and thanks to you but I'm trying<00:02:07.229> to<00:02:07.259> finish<00:02:07.500> a<00:02:07.619> book<00:02:08.479> thank<00:02:09.479> selected 00:02:09.919 --> 00:02:09.929 align:start position:0% trying to finish a book thank selected 00:02:09.929 --> 00:02:11.949 align:start position:0% trying to finish a book thank selected for<00:02:10.110> an<00:02:10.259> invitation<00:02:10.470> because<00:02:11.099> that<00:02:11.489> kind<00:02:11.760> of 00:02:11.949 --> 00:02:11.959 align:start position:0% for an invitation because that kind of 00:02:11.959 --> 00:02:14.080 align:start position:0% for an invitation because that kind of we're<00:02:12.109> trying<00:02:12.799> to<00:02:12.920> grow<00:02:13.040> these<00:02:13.400> slides 00:02:14.080 --> 00:02:14.090 align:start position:0% we're trying to grow these slides 00:02:14.090 --> 00:02:16.449 align:start position:0% we're trying to grow these slides together<00:02:14.299> in<00:02:14.719> a<00:02:14.840> short<00:02:15.079> monograph<00:02:15.650> which<00:02:16.340> is 00:02:16.449 --> 00:02:16.459 align:start position:0% together in a short monograph which is 00:02:16.459 --> 00:02:18.069 align:start position:0% together in a short monograph which is mostly<00:02:16.730> about<00:02:16.909> the<00:02:17.060> practice<00:02:17.540> of<00:02:17.689> labeling 00:02:18.069 --> 00:02:18.079 align:start position:0% mostly about the practice of labeling 00:02:18.079 --> 00:02:20.589 align:start position:0% mostly about the practice of labeling mm-hmm<00:02:18.680> there's<00:02:19.069> a<00:02:19.159> lot<00:02:19.340> of<00:02:19.519> publications<00:02:20.180> on 00:02:20.589 --> 00:02:20.599 align:start position:0% mm-hmm there's a lot of publications on 00:02:20.599 --> 00:02:24.220 align:start position:0% mm-hmm there's a lot of publications on how<00:02:20.689> to<00:02:20.750> do<00:02:21.519> labeling<00:02:22.519> but<00:02:22.760> the<00:02:23.209> bulk<00:02:23.450> is<00:02:23.810> how 00:02:24.220 --> 00:02:24.230 align:start position:0% how to do labeling but the bulk is how 00:02:24.230 --> 00:02:26.860 align:start position:0% how to do labeling but the bulk is how to<00:02:24.290> do<00:02:24.500> this<00:02:24.650> at<00:02:25.310> scale<00:02:25.640> and<00:02:26.299> involves 00:02:26.860 --> 00:02:26.870 align:start position:0% to do this at scale and involves 00:02:26.870 --> 00:02:29.110 align:start position:0% to do this at scale and involves learning<00:02:27.319> how<00:02:27.560> to<00:02:27.590> design<00:02:28.010> your<00:02:28.069> hits<00:02:28.760> your 00:02:29.110 --> 00:02:29.120 align:start position:0% learning how to design your hits your 00:02:29.120 --> 00:02:31.449 align:start position:0% learning how to design your hits your human<00:02:29.599> intelligent<00:02:30.019> tasks<00:02:30.409> and<00:02:30.560> then<00:02:31.189> based 00:02:31.449 --> 00:02:31.459 align:start position:0% human intelligent tasks and then based 00:02:31.459 --> 00:02:32.559 align:start position:0% human intelligent tasks and then based on<00:02:31.579> the<00:02:31.670> domain<00:02:31.819> applying<00:02:32.420> different 00:02:32.559 --> 00:02:32.569 align:start position:0% on the domain applying different 00:02:32.569 --> 00:02:34.929 align:start position:0% on the domain applying different techniques<00:02:33.439> that's<00:02:33.829> basically<00:02:34.280> the<00:02:34.579> the 00:02:34.929 --> 00:02:34.939 align:start position:0% techniques that's basically the the 00:02:34.939 --> 00:02:36.970 align:start position:0% techniques that's basically the the practice<00:02:35.420> so<00:02:35.989> this<00:02:36.109> is<00:02:36.170> I<00:02:36.319> think<00:02:36.469> you<00:02:36.829> know 00:02:36.970 --> 00:02:36.980 align:start position:0% practice so this is I think you know 00:02:36.980 --> 00:02:38.770 align:start position:0% practice so this is I think you know when<00:02:37.250> I<00:02:37.430> think<00:02:37.519> when<00:02:37.819> you<00:02:37.879> did<00:02:38.060> this<00:02:38.180> talk<00:02:38.450> the 00:02:38.770 --> 00:02:38.780 align:start position:0% when I think when you did this talk the 00:02:38.780 --> 00:02:43.390 align:start position:0% when I think when you did this talk the whole<00:02:38.930> like<00:02:39.230> AI<00:02:40.129> wave<00:02:40.549> was<00:02:40.909> not<00:02:41.090> as<00:02:41.269> fine<00:02:41.450> as<00:02:42.400> it 00:02:43.390 --> 00:02:43.400 align:start position:0% whole like AI wave was not as fine as it 00:02:43.400 --> 00:02:44.949 align:start position:0% whole like AI wave was not as fine as it is<00:02:43.519> to<00:02:43.670> me<00:02:43.819> and<00:02:44.090> now<00:02:44.239> I<00:02:44.269> think<00:02:44.419> what<00:02:44.780> should<00:02:44.900> we 00:02:44.949 --> 00:02:44.959 align:start position:0% is to me and now I think what should we 00:02:44.959 --> 00:02:47.649 align:start position:0% is to me and now I think what should we see<00:02:45.109> better<00:02:45.230> relevant<00:02:46.329> examples<00:02:47.329> right 00:02:47.649 --> 00:02:47.659 align:start position:0% see better relevant examples right 00:02:47.659 --> 00:02:50.409 align:start position:0% see better relevant examples right because<00:02:47.959> the<00:02:48.769> trust<00:02:49.189> in<00:02:49.579> machine<00:02:50.269> learning 00:02:50.409 --> 00:02:50.419 align:start position:0% because the trust in machine learning 00:02:50.419 --> 00:02:53.740 align:start position:0% because the trust in machine learning now<00:02:51.349> I<00:02:51.379> think<00:02:51.769> more<00:02:52.099> people<00:02:52.189> understand<00:02:52.760> and<00:02:53.419> I 00:02:53.740 --> 00:02:53.750 align:start position:0% now I think more people understand and I 00:02:53.750 --> 00:02:56.289 align:start position:0% now I think more people understand and I think<00:02:53.959> there<00:02:54.109> were<00:02:54.280> like<00:02:55.280> mainstream<00:02:55.579> media 00:02:56.289 --> 00:02:56.299 align:start position:0% think there were like mainstream media 00:02:56.299 --> 00:02:59.500 align:start position:0% think there were like mainstream media articles<00:02:56.810> about<00:02:57.079> bias<00:02:57.650> right<00:02:58.519> so<00:02:58.849> if<00:02:59.180> you<00:02:59.389> know 00:02:59.500 --> 00:02:59.510 align:start position:0% articles about bias right so if you know 00:02:59.510 --> 00:03:01.270 align:start position:0% articles about bias right so if you know i<00:02:59.540> strangle<00:03:00.139> certain<00:03:00.379> kind<00:03:00.530> of<00:03:00.620> people<00:03:00.980> it 00:03:01.270 --> 00:03:01.280 align:start position:0% i strangle certain kind of people it 00:03:01.280 --> 00:03:02.619 align:start position:0% i strangle certain kind of people it will<00:03:01.519> not<00:03:01.790> understand<00:03:02.180> all<00:03:02.269> the<00:03:02.359> kind<00:03:02.540> of 00:03:02.619 --> 00:03:02.629 align:start position:0% will not understand all the kind of 00:03:02.629 --> 00:03:05.170 align:start position:0% will not understand all the kind of people<00:03:02.959> their<00:03:03.230> voices<00:03:03.879> right<00:03:04.879> like<00:03:05.060> the 00:03:05.170 --> 00:03:05.180 align:start position:0% people their voices right like the 00:03:05.180 --> 00:03:06.970 align:start position:0% people their voices right like the characteristics<00:03:05.840> and<00:03:05.900> so<00:03:06.049> forth<00:03:06.260> so<00:03:06.409> so<00:03:06.889> I'm 00:03:06.970 --> 00:03:06.980 align:start position:0% characteristics and so forth so so I'm 00:03:06.980 --> 00:03:09.360 align:start position:0% characteristics and so forth so so I'm wondering<00:03:07.280> kind<00:03:08.209> of<00:03:08.359> do<00:03:08.629> you<00:03:08.719> find<00:03:09.019> that 00:03:09.360 --> 00:03:09.370 align:start position:0% wondering kind of do you find that 00:03:09.370 --> 00:03:12.520 align:start position:0% wondering kind of do you find that people<00:03:10.370> understand<00:03:11.239> that<00:03:11.389> the<00:03:11.569> talk<00:03:11.750> comes 00:03:12.520 --> 00:03:12.530 align:start position:0% people understand that the talk comes 00:03:12.530 --> 00:03:15.159 align:start position:0% people understand that the talk comes down<00:03:12.739> to<00:03:13.010> the<00:03:13.159> data<00:03:13.400> originally<00:03:14.269> like<00:03:14.900> did<00:03:15.079> you 00:03:15.159 --> 00:03:15.169 align:start position:0% down to the data originally like did you 00:03:15.169 --> 00:03:16.960 align:start position:0% down to the data originally like did you see<00:03:15.530> more<00:03:15.889> people<00:03:16.099> asking<00:03:16.400> you<00:03:16.549> about<00:03:16.579> this 00:03:16.960 --> 00:03:16.970 align:start position:0% see more people asking you about this 00:03:16.970 --> 00:03:19.899 align:start position:0% see more people asking you about this like<00:03:17.150> :<00:03:17.540> to<00:03:17.720> amp<00:03:17.930> the<00:03:18.229> data<00:03:18.409> quality<00:03:18.590> oh<00:03:19.220> boy 00:03:19.899 --> 00:03:19.909 align:start position:0% like : to amp the data quality oh boy 00:03:19.909 --> 00:03:22.030 align:start position:0% like : to amp the data quality oh boy yes<00:03:20.389> so<00:03:20.690> the<00:03:21.139> answer<00:03:21.349> is<00:03:21.470> yes<00:03:21.650> people<00:03:21.889> are 00:03:22.030 --> 00:03:22.040 align:start position:0% yes so the answer is yes people are 00:03:22.040 --> 00:03:23.979 align:start position:0% yes so the answer is yes people are getting<00:03:22.760> more<00:03:22.909> interesting<00:03:23.120> and<00:03:23.449> how<00:03:23.540> to<00:03:23.599> how 00:03:23.979 --> 00:03:23.989 align:start position:0% getting more interesting and how to how 00:03:23.989 --> 00:03:26.409 align:start position:0% getting more interesting and how to how do<00:03:24.049> I<00:03:24.199> build<00:03:24.319> training<00:03:25.159> sets<00:03:25.400> how<00:03:25.729> do<00:03:25.790> I<00:03:25.970> assess 00:03:26.409 --> 00:03:26.419 align:start position:0% do I build training sets how do I assess 00:03:26.419 --> 00:03:27.789 align:start position:0% do I build training sets how do I assess the<00:03:26.569> quality<00:03:26.659> of<00:03:27.049> my<00:03:27.199> machine<00:03:27.530> learning 00:03:27.789 --> 00:03:27.799 align:start position:0% the quality of my machine learning 00:03:27.799 --> 00:03:31.030 align:start position:0% the quality of my machine learning models<00:03:28.189> ai<00:03:28.370> models<00:03:28.909> at<00:03:29.449> the<00:03:29.510> same<00:03:29.840> time<00:03:30.079> biases 00:03:31.030 --> 00:03:31.040 align:start position:0% models ai models at the same time biases 00:03:31.040 --> 00:03:33.099 align:start position:0% models ai models at the same time biases is<00:03:31.250> and<00:03:31.549> you<00:03:31.639> think<00:03:31.699> that<00:03:32.000> is<00:03:32.120> coming<00:03:32.569> up<00:03:32.780> a<00:03:32.930> lot 00:03:33.099 --> 00:03:33.109 align:start position:0% is and you think that is coming up a lot 00:03:33.109 --> 00:03:35.649 align:start position:0% is and you think that is coming up a lot and<00:03:33.859> last<00:03:34.280> but<00:03:34.489> not<00:03:34.699> least<00:03:34.970> the<00:03:35.180> notion<00:03:35.540> of 00:03:35.649 --> 00:03:35.659 align:start position:0% and last but not least the notion of 00:03:35.659 --> 00:03:38.890 align:start position:0% and last but not least the notion of annotations<00:03:36.409> on<00:03:36.760> labeling<00:03:37.760> datasets<00:03:38.239> because 00:03:38.890 --> 00:03:38.900 align:start position:0% annotations on labeling datasets because 00:03:38.900 --> 00:03:40.390 align:start position:0% annotations on labeling datasets because sometimes<00:03:39.349> you<00:03:39.439> don't<00:03:39.530> know<00:03:39.769> how<00:03:40.010> you<00:03:40.069> gather 00:03:40.390 --> 00:03:40.400 align:start position:0% sometimes you don't know how you gather 00:03:40.400 --> 00:03:43.210 align:start position:0% sometimes you don't know how you gather this<00:03:40.639> data<00:03:41.090> sets<00:03:41.449> right<00:03:41.720> so<00:03:42.229> I<00:03:42.259> don't<00:03:42.500> even<00:03:42.620> I 00:03:43.210 --> 00:03:43.220 align:start position:0% this data sets right so I don't even I 00:03:43.220 --> 00:03:46.719 align:start position:0% this data sets right so I don't even I was<00:03:43.669> the<00:03:43.879> sampling<00:03:44.359> methodology<00:03:44.889> which<00:03:45.889> areas 00:03:46.719 --> 00:03:46.729 align:start position:0% was the sampling methodology which areas 00:03:46.729 --> 00:03:50.349 align:start position:0% was the sampling methodology which areas we<00:03:46.879> touch<00:03:47.470> etcetera<00:03:48.470> etc<00:03:48.530> is<00:03:49.189> usually<00:03:49.909> not 00:03:50.349 --> 00:03:50.359 align:start position:0% we touch etcetera etc is usually not 00:03:50.359 --> 00:03:53.589 align:start position:0% we touch etcetera etc is usually not even<00:03:51.040> thought<00:03:52.040> and<00:03:52.549> it's<00:03:52.819> it's<00:03:53.120> been<00:03:53.209> it's 00:03:53.589 --> 00:03:53.599 align:start position:0% even thought and it's it's been it's 00:03:53.599 --> 00:03:55.270 align:start position:0% even thought and it's it's been it's becoming<00:03:53.989> an<00:03:54.139> crucial<00:03:54.530> because<00:03:54.979> you<00:03:55.069> want 00:03:55.270 --> 00:03:55.280 align:start position:0% becoming an crucial because you want 00:03:55.280 --> 00:03:58.360 align:start position:0% becoming an crucial because you want labels<00:03:56.000> you<00:03:56.629> want<00:03:56.659> clean<00:03:57.470> the<00:03:57.620> reset<00:03:57.919> and<00:03:58.159> then 00:03:58.360 --> 00:03:58.370 align:start position:0% labels you want clean the reset and then 00:03:58.370 --> 00:03:59.949 align:start position:0% labels you want clean the reset and then you<00:03:58.609> not<00:03:58.790> only<00:03:58.819> you<00:03:59.060> want<00:03:59.239> to<00:03:59.419> know<00:03:59.569> how<00:03:59.720> buys 00:03:59.949 --> 00:03:59.959 align:start position:0% you not only you want to know how buys 00:03:59.959 --> 00:04:01.449 align:start position:0% you not only you want to know how buys the<00:04:00.109> data<00:04:00.290> studies<00:04:00.590> but<00:04:01.099> also<00:04:01.159> you<00:04:01.310> want<00:04:01.430> to 00:04:01.449 --> 00:04:01.459 align:start position:0% the data studies but also you want to 00:04:01.459 --> 00:04:02.860 align:start position:0% the data studies but also you want to know<00:04:01.579> all<00:04:01.790> the<00:04:01.909> annotations<00:04:02.090> so<00:04:02.569> if<00:04:02.629> you<00:04:02.720> want 00:04:02.860 --> 00:04:02.870 align:start position:0% know all the annotations so if you want 00:04:02.870 --> 00:04:06.099 align:start position:0% know all the annotations so if you want to<00:04:03.079> reproduce<00:04:04.449> another<00:04:05.449> experiment<00:04:05.959> so<00:04:06.019> you 00:04:06.099 --> 00:04:06.109 align:start position:0% to reproduce another experiment so you 00:04:06.109 --> 00:04:08.559 align:start position:0% to reproduce another experiment so you know<00:04:06.259> to<00:04:06.470> refresh<00:04:07.009> a<00:04:07.040> data<00:04:07.310> set<00:04:07.579> you<00:04:08.299> have<00:04:08.329> to 00:04:08.559 --> 00:04:08.569 align:start position:0% know to refresh a data set you have to 00:04:08.569 --> 00:04:10.059 align:start position:0% know to refresh a data set you have to have<00:04:08.720> all<00:04:08.900> the<00:04:08.989> different<00:04:09.109> knobs<00:04:09.680> that<00:04:10.009> you 00:04:10.059 --> 00:04:10.069 align:start position:0% have all the different knobs that you 00:04:10.069 --> 00:04:12.339 align:start position:0% have all the different knobs that you used<00:04:10.400> to<00:04:10.639> build<00:04:10.849> this<00:04:11.030> data<00:04:11.269> set<00:04:11.509> which<00:04:12.139> in<00:04:12.259> the 00:04:12.339 --> 00:04:12.349 align:start position:0% used to build this data set which in the 00:04:12.349 --> 00:04:15.219 align:start position:0% used to build this data set which in the past<00:04:12.500> was<00:04:12.739> like<00:04:12.829> God<00:04:13.819> gives<00:04:14.150> Alex<00:04:14.540> a<00:04:14.750> data<00:04:15.019> set 00:04:15.219 --> 00:04:15.229 align:start position:0% past was like God gives Alex a data set 00:04:15.229 --> 00:04:17.140 align:start position:0% past was like God gives Alex a data set it<00:04:15.349> was<00:04:15.439> right<00:04:15.620> that's<00:04:15.949> good<00:04:16.130> now<00:04:16.699> it's<00:04:16.970> like 00:04:17.140 --> 00:04:17.150 align:start position:0% it was right that's good now it's like 00:04:17.150 --> 00:04:19.629 align:start position:0% it was right that's good now it's like you<00:04:17.750> have<00:04:17.900> to<00:04:18.139> derive<00:04:18.530> these<00:04:18.769> data<00:04:19.099> sets<00:04:19.340> over 00:04:19.629 --> 00:04:19.639 align:start position:0% you have to derive these data sets over 00:04:19.639 --> 00:04:21.009 align:start position:0% you have to derive these data sets over and<00:04:19.759> over<00:04:19.880> again<00:04:20.000> for<00:04:20.269> million<00:04:20.570> different 00:04:21.009 --> 00:04:21.019 align:start position:0% and over again for million different 00:04:21.019 --> 00:04:23.920 align:start position:0% and over again for million different properties<00:04:21.709> and<00:04:21.979> domains<00:04:22.430> so<00:04:23.120> you<00:04:23.630> know<00:04:23.750> what 00:04:23.920 --> 00:04:23.930 align:start position:0% properties and domains so you know what 00:04:23.930 --> 00:04:25.540 align:start position:0% properties and domains so you know what comes<00:04:24.110> to<00:04:24.229> mind<00:04:24.410> is<00:04:24.560> rather<00:04:24.710> let's<00:04:25.190> say<00:04:25.310> what's 00:04:25.540 --> 00:04:25.550 align:start position:0% comes to mind is rather let's say what's 00:04:25.550 --> 00:04:27.939 align:start position:0% comes to mind is rather let's say what's this<00:04:25.940> called<00:04:26.150> fake<00:04:26.360> news<00:04:26.690> phenomena<00:04:27.319> no<00:04:27.560> right 00:04:27.939 --> 00:04:27.949 align:start position:0% this called fake news phenomena no right 00:04:27.949 --> 00:04:30.999 align:start position:0% this called fake news phenomena no right obviously<00:04:28.280> news<00:04:29.650> people<00:04:30.650> have<00:04:30.770> different 00:04:30.999 --> 00:04:31.009 align:start position:0% obviously news people have different 00:04:31.009 --> 00:04:33.219 align:start position:0% obviously news people have different opinions<00:04:31.400> so<00:04:31.669> if<00:04:31.759> you<00:04:31.849> ask<00:04:32.090> if<00:04:32.419> you<00:04:32.509> want<00:04:32.720> to 00:04:33.219 --> 00:04:33.229 align:start position:0% opinions so if you ask if you want to 00:04:33.229 --> 00:04:35.800 align:start position:0% opinions so if you ask if you want to ask<00:04:33.560> a<00:04:33.680> bunch<00:04:33.800> of<00:04:33.889> people<00:04:34.130> to<00:04:34.250> label<00:04:34.810> political 00:04:35.800 --> 00:04:35.810 align:start position:0% ask a bunch of people to label political 00:04:35.810 --> 00:04:38.379 align:start position:0% ask a bunch of people to label political tweets<00:04:36.340> Russians<00:04:37.340> will<00:04:37.520> label<00:04:37.910> them<00:04:38.210> very 00:04:38.379 --> 00:04:38.389 align:start position:0% tweets Russians will label them very 00:04:38.389 --> 00:04:40.360 align:start position:0% tweets Russians will label them very different<00:04:38.720> than<00:04:38.990> Americans<00:04:39.440> in<00:04:39.770> Russian 00:04:40.360 --> 00:04:40.370 align:start position:0% different than Americans in Russian 00:04:40.370 --> 00:04:42.279 align:start position:0% different than Americans in Russian Americans<00:04:40.880> will<00:04:41.120> label<00:04:41.360> them<00:04:41.569> different<00:04:42.050> from 00:04:42.279 --> 00:04:42.289 align:start position:0% Americans will label them different from 00:04:42.289 --> 00:04:44.620 align:start position:0% Americans will label them different from either<00:04:42.740> of<00:04:42.889> these<00:04:43.099> groups<00:04:43.400> yes<00:04:43.699> right<00:04:44.150> and<00:04:44.419> so 00:04:44.620 --> 00:04:44.630 align:start position:0% either of these groups yes right and so 00:04:44.630 --> 00:04:48.070 align:start position:0% either of these groups yes right and so so<00:04:45.050> I<00:04:45.620> wonder<00:04:46.220> do<00:04:46.550> you<00:04:46.669> find<00:04:47.000> like<00:04:47.300> they<00:04:47.630> do<00:04:47.870> try 00:04:48.070 --> 00:04:48.080 align:start position:0% so I wonder do you find like they do try 00:04:48.080 --> 00:04:49.330 align:start position:0% so I wonder do you find like they do try to<00:04:48.110> compensate<00:04:48.650> for<00:04:48.740> this<00:04:48.860> they<00:04:49.069> want<00:04:49.220> to 00:04:49.330 --> 00:04:49.340 align:start position:0% to compensate for this they want to 00:04:49.340 --> 00:04:51.850 align:start position:0% to compensate for this they want to understand<00:04:49.669> what<00:04:49.819> biases<00:04:50.240> like<00:04:50.449> humans<00:04:51.349> have 00:04:51.850 --> 00:04:51.860 align:start position:0% understand what biases like humans have 00:04:51.860 --> 00:04:54.309 align:start position:0% understand what biases like humans have biases<00:04:52.280> and<00:04:52.819> like<00:04:53.270> do<00:04:53.599> you<00:04:53.720> want<00:04:53.930> to<00:04:54.020> go<00:04:54.139> back 00:04:54.309 --> 00:04:54.319 align:start position:0% biases and like do you want to go back 00:04:54.319 --> 00:04:56.020 align:start position:0% biases and like do you want to go back to<00:04:54.530> them<00:04:54.710> and<00:04:54.919> understand<00:04:55.460> what<00:04:55.580> biases<00:04:55.909> they 00:04:56.020 --> 00:04:56.030 align:start position:0% to them and understand what biases they 00:04:56.030 --> 00:04:58.629 align:start position:0% to them and understand what biases they could<00:04:56.180> have<00:04:56.360> had<00:04:56.569> like<00:04:57.349> how<00:04:57.500> do<00:04:58.190> we<00:04:58.400> have<00:04:58.550> to 00:04:58.629 --> 00:04:58.639 align:start position:0% could have had like how do we have to 00:04:58.639 --> 00:05:00.820 align:start position:0% could have had like how do we have to understand<00:04:59.030> biases<00:04:59.389> in<00:04:59.509> humans<00:04:59.900> like<00:05:00.289> do<00:05:00.740> we 00:05:00.820 --> 00:05:00.830 align:start position:0% understand biases in humans like do we 00:05:00.830 --> 00:05:02.080 align:start position:0% understand biases in humans like do we have<00:05:00.979> to<00:05:01.039> go<00:05:01.159> back<00:05:01.340> all<00:05:01.550> the<00:05:01.580> way<00:05:01.699> and<00:05:01.789> try<00:05:02.030> to 00:05:02.080 --> 00:05:02.090 align:start position:0% have to go back all the way and try to 00:05:02.090 --> 00:05:04.510 align:start position:0% have to go back all the way and try to model<00:05:02.449> I<00:05:02.659> think<00:05:03.259> what<00:05:03.560> you<00:05:03.620> need<00:05:03.650> to<00:05:03.889> you<00:05:04.430> need 00:05:04.510 --> 00:05:04.520 align:start position:0% model I think what you need to you need 00:05:04.520 --> 00:05:06.399 align:start position:0% model I think what you need to you need to<00:05:04.669> do<00:05:05.000> if<00:05:05.389> you're<00:05:05.569> going<00:05:05.690> to<00:05:05.780> build<00:05:05.960> a<00:05:06.139> set<00:05:06.319> of 00:05:06.399 --> 00:05:06.409 align:start position:0% to do if you're going to build a set of 00:05:06.409 --> 00:05:09.040 align:start position:0% to do if you're going to build a set of sets<00:05:06.590> is<00:05:06.770> to<00:05:07.009> you<00:05:07.159> get<00:05:07.940> an<00:05:08.030> idea<00:05:08.330> if<00:05:08.630> the<00:05:08.780> task 00:05:09.040 --> 00:05:09.050 align:start position:0% sets is to you get an idea if the task 00:05:09.050 --> 00:05:12.040 align:start position:0% sets is to you get an idea if the task has<00:05:09.440> a<00:05:09.470> subjective<00:05:10.340> answer<00:05:10.460> an<00:05:11.449> objective 00:05:12.040 --> 00:05:12.050 align:start position:0% has a subjective answer an objective 00:05:12.050 --> 00:05:14.409 align:start position:0% has a subjective answer an objective answer<00:05:12.199> or<00:05:12.650> somewhere<00:05:13.069> in<00:05:13.159> the<00:05:13.190> middle<00:05:13.250> so<00:05:14.210> yes 00:05:14.409 --> 00:05:14.419 align:start position:0% answer or somewhere in the middle so yes 00:05:14.419 --> 00:05:16.779 align:start position:0% answer or somewhere in the middle so yes if<00:05:14.720> the<00:05:15.020> task<00:05:15.259> is<00:05:15.500> about<00:05:15.620> building<00:05:15.889> objective 00:05:16.779 --> 00:05:16.789 align:start position:0% if the task is about building objective 00:05:16.789 --> 00:05:18.879 align:start position:0% if the task is about building objective answers<00:05:17.330> then<00:05:17.599> you<00:05:17.630> can<00:05:18.139> get<00:05:18.229> agreements<00:05:18.740> and 00:05:18.879 --> 00:05:18.889 align:start position:0% answers then you can get agreements and 00:05:18.889 --> 00:05:21.010 align:start position:0% answers then you can get agreements and compute<00:05:19.370> in<00:05:19.759> traded<00:05:20.240> coefficients<00:05:20.900> etcetera 00:05:21.010 --> 00:05:21.020 align:start position:0% compute in traded coefficients etcetera 00:05:21.020 --> 00:05:23.649 align:start position:0% compute in traded coefficients etcetera there<00:05:21.949> are<00:05:22.039> certain<00:05:22.220> things<00:05:22.430> like<00:05:22.659> election 00:05:23.649 --> 00:05:23.659 align:start position:0% there are certain things like election 00:05:23.659 --> 00:05:25.510 align:start position:0% there are certain things like election as<00:05:23.780> Democrats<00:05:24.319> versus<00:05:24.710> Republicans<00:05:24.740> you<00:05:25.430> know 00:05:25.510 --> 00:05:25.520 align:start position:0% as Democrats versus Republicans you know 00:05:25.520 --> 00:05:28.029 align:start position:0% as Democrats versus Republicans you know fake<00:05:25.759> news<00:05:26.000> versus<00:05:26.360> no<00:05:26.539> fake<00:05:26.780> news<00:05:27.020> those<00:05:27.349> tend 00:05:28.029 --> 00:05:28.039 align:start position:0% fake news versus no fake news those tend 00:05:28.039 --> 00:05:31.029 align:start position:0% fake news versus no fake news those tend to<00:05:28.159> get<00:05:28.340> much<00:05:28.849> harder<00:05:29.210> so<00:05:30.020> it's<00:05:30.560> difficult<00:05:30.710> to 00:05:31.029 --> 00:05:31.039 align:start position:0% to get much harder so it's difficult to 00:05:31.039 --> 00:05:33.399 align:start position:0% to get much harder so it's difficult to get<00:05:31.190> full<00:05:32.150> agreement<00:05:32.599> but<00:05:32.750> what<00:05:33.080> you<00:05:33.169> want<00:05:33.349> to 00:05:33.399 --> 00:05:33.409 align:start position:0% get full agreement but what you want to 00:05:33.409 --> 00:05:35.890 align:start position:0% get full agreement but what you want to know<00:05:33.800> is<00:05:34.159> if<00:05:34.610> you<00:05:34.820> sample<00:05:35.030> different<00:05:35.630> times 00:05:35.890 --> 00:05:35.900 align:start position:0% know is if you sample different times 00:05:35.900 --> 00:05:38.950 align:start position:0% know is if you sample different times the<00:05:36.320> proportions<00:05:37.039> are<00:05:37.250> stable<00:05:37.909> which<00:05:38.750> means 00:05:38.950 --> 00:05:38.960 align:start position:0% the proportions are stable which means 00:05:38.960 --> 00:05:42.700 align:start position:0% the proportions are stable which means like<00:05:39.199> well<00:05:39.469> if<00:05:39.860> 205<00:05:40.849> thing<00:05:41.180> it's<00:05:41.360> fake<00:05:41.710> always 00:05:42.700 --> 00:05:42.710 align:start position:0% like well if 205 thing it's fake always 00:05:42.710 --> 00:05:45.399 align:start position:0% like well if 205 thing it's fake always maybe<00:05:43.280> there's<00:05:43.490> something<00:05:43.699> there<00:05:44.080> buddy<00:05:45.080> one 00:05:45.399 --> 00:05:45.409 align:start position:0% maybe there's something there buddy one 00:05:45.409 --> 00:05:47.170 align:start position:0% maybe there's something there buddy one sample<00:05:45.650> nobody<00:05:46.370> thinks<00:05:46.580> is<00:05:46.639> fixed<00:05:46.969> on<00:05:47.060> the 00:05:47.170 --> 00:05:47.180 align:start position:0% sample nobody thinks is fixed on the 00:05:47.180 --> 00:05:49.110 align:start position:0% sample nobody thinks is fixed on the next<00:05:47.389> one<00:05:47.509> everyone<00:05:47.840> thinks<00:05:48.020> it's<00:05:48.110> fake<00:05:48.380> then 00:05:49.110 --> 00:05:49.120 align:start position:0% next one everyone thinks it's fake then 00:05:49.120 --> 00:05:51.399 align:start position:0% next one everyone thinks it's fake then you<00:05:50.120> know<00:05:50.270> there's<00:05:50.569> something<00:05:50.750> fishy<00:05:51.050> there 00:05:51.399 --> 00:05:51.409 align:start position:0% you know there's something fishy there 00:05:51.409 --> 00:05:56.350 align:start position:0% you know there's something fishy there right<00:05:51.860> so<00:05:52.099> it's<00:05:52.639> more<00:05:52.849> about<00:05:53.229> trying<00:05:54.229> to<00:05:55.360> find 00:05:56.350 --> 00:05:56.360 align:start position:0% right so it's more about trying to find 00:05:56.360 --> 00:05:58.540 align:start position:0% right so it's more about trying to find those<00:05:56.630> tasks<00:05:56.930> were<00:05:57.199> things<00:05:58.009> you're<00:05:58.280> not<00:05:58.400> going 00:05:58.540 --> 00:05:58.550 align:start position:0% those tasks were things you're not going 00:05:58.550 --> 00:06:00.249 align:start position:0% those tasks were things you're not going to<00:05:58.610> get<00:05:58.669> agreement<00:05:58.909> on<00:05:59.180> it<00:05:59.360> and<00:05:59.930> then<00:06:00.080> do 00:06:00.249 --> 00:06:00.259 align:start position:0% to get agreement on it and then do 00:06:00.259 --> 00:06:02.950 align:start position:0% to get agreement on it and then do something<00:06:00.530> with<00:06:00.830> it<00:06:00.949> versus<00:06:01.819> blindly<00:06:02.360> you 00:06:02.950 --> 00:06:02.960 align:start position:0% something with it versus blindly you 00:06:02.960 --> 00:06:05.050 align:start position:0% something with it versus blindly you know<00:06:03.110> either<00:06:03.409> either<00:06:03.860> blaming<00:06:04.370> the<00:06:04.610> data<00:06:04.789> set 00:06:05.050 --> 00:06:05.060 align:start position:0% know either either blaming the data set 00:06:05.060 --> 00:06:07.839 align:start position:0% know either either blaming the data set or<00:06:05.330> the<00:06:05.599> workers<00:06:06.050> or<00:06:06.500> the<00:06:06.800> interactions<00:06:07.340> which 00:06:07.839 --> 00:06:07.849 align:start position:0% or the workers or the interactions which 00:06:07.849 --> 00:06:09.240 align:start position:0% or the workers or the interactions which is<00:06:08.000> usually<00:06:08.330> what<00:06:08.479> is<00:06:08.569> done<00:06:08.599> in<00:06:08.840> practice 00:06:09.240 --> 00:06:09.250 align:start position:0% is usually what is done in practice 00:06:09.250 --> 00:06:11.589 align:start position:0% is usually what is done in practice understanding<00:06:10.250> the<00:06:10.699> nature<00:06:10.880> of<00:06:11.120> the<00:06:11.210> problem 00:06:11.589 --> 00:06:11.599 align:start position:0% understanding the nature of the problem 00:06:11.599 --> 00:06:13.480 align:start position:0% understanding the nature of the problem fake<00:06:11.870> news<00:06:12.110> detection<00:06:12.530> is<00:06:12.650> hard<00:06:12.919> mm-hmm 00:06:13.480 --> 00:06:13.490 align:start position:0% fake news detection is hard mm-hmm 00:06:13.490 --> 00:06:15.070 align:start position:0% fake news detection is hard mm-hmm because<00:06:13.909> like<00:06:14.090> I<00:06:14.120> said<00:06:14.449> if<00:06:14.630> you<00:06:14.750> think<00:06:14.990> in 00:06:15.070 --> 00:06:15.080 align:start position:0% because like I said if you think in 00:06:15.080 --> 00:06:17.320 align:start position:0% because like I said if you think in terms<00:06:15.110> of<00:06:15.469> US<00:06:15.830> vs.<00:06:16.340> Russian<00:06:16.699> politics<00:06:17.030> is<00:06:17.210> one 00:06:17.320 --> 00:06:17.330 align:start position:0% terms of US vs. Russian politics is one 00:06:17.330 --> 00:06:19.779 align:start position:0% terms of US vs. Russian politics is one thing<00:06:17.539> but<00:06:17.810> if<00:06:18.259> you<00:06:18.409> say<00:06:18.560> faking<00:06:19.159> news<00:06:19.310> about<00:06:19.729> a 00:06:19.779 --> 00:06:19.789 align:start position:0% thing but if you say faking news about a 00:06:19.789 --> 00:06:21.430 align:start position:0% thing but if you say faking news about a brexit<00:06:20.479> maybe<00:06:20.780> it's<00:06:20.960> a<00:06:20.990> whole<00:06:21.139> different 00:06:21.430 --> 00:06:21.440 align:start position:0% brexit maybe it's a whole different 00:06:21.440 --> 00:06:23.950 align:start position:0% brexit maybe it's a whole different thing<00:06:21.469> right<00:06:21.979> maybe<00:06:22.610> people<00:06:23.000> make<00:06:23.180> get<00:06:23.780> more 00:06:23.950 --> 00:06:23.960 align:start position:0% thing right maybe people make get more 00:06:23.960 --> 00:06:26.350 align:start position:0% thing right maybe people make get more agreement<00:06:24.349> on<00:06:24.409> fake<00:06:24.710> news<00:06:24.949> in<00:06:25.130> Rex's<00:06:25.550> versus 00:06:26.350 --> 00:06:26.360 align:start position:0% agreement on fake news in Rex's versus 00:06:26.360 --> 00:06:28.029 align:start position:0% agreement on fake news in Rex's versus politics<00:06:26.990> in<00:06:27.080> the<00:06:27.139> u.s.<00:06:27.380> right<00:06:27.710> so 00:06:28.029 --> 00:06:28.039 align:start position:0% politics in the u.s. right so 00:06:28.039 --> 00:06:30.100 align:start position:0% politics in the u.s. right so understanding<00:06:28.610> that<00:06:28.789> I<00:06:28.849> think<00:06:29.330> is<00:06:29.479> kind<00:06:29.990> of 00:06:30.100 --> 00:06:30.110 align:start position:0% understanding that I think is kind of 00:06:30.110 --> 00:06:31.510 align:start position:0% understanding that I think is kind of the<00:06:30.199> precondition<00:06:30.860> for<00:06:30.889> doing<00:06:31.250> the<00:06:31.339> rest 00:06:31.510 --> 00:06:31.520 align:start position:0% the precondition for doing the rest 00:06:31.520 --> 00:06:33.810 align:start position:0% the precondition for doing the rest right<00:06:31.940> and<00:06:32.150> fake<00:06:32.419> maybe<00:06:33.020> I<00:06:33.199> mean 00:06:33.810 --> 00:06:33.820 align:start position:0% right and fake maybe I mean 00:06:33.820 --> 00:06:35.490 align:start position:0% right and fake maybe I mean an<00:06:34.090> objective<00:06:34.420> through<00:06:34.930> like<00:06:35.140> something 00:06:35.490 --> 00:06:35.500 align:start position:0% an objective through like something 00:06:35.500 --> 00:06:38.430 align:start position:0% an objective through like something happened<00:06:35.890> and<00:06:36.070> news<00:06:36.630> is<00:06:37.630> wrong<00:06:37.960> then<00:06:38.290> you<00:06:38.380> can 00:06:38.430 --> 00:06:38.440 align:start position:0% happened and news is wrong then you can 00:06:38.440 --> 00:06:39.690 align:start position:0% happened and news is wrong then you can say<00:06:38.620> it's<00:06:38.740> fake<00:06:38.890> but<00:06:39.070> if<00:06:39.280> something<00:06:39.610> is 00:06:39.690 --> 00:06:39.700 align:start position:0% say it's fake but if something is 00:06:39.700 --> 00:06:41.310 align:start position:0% say it's fake but if something is political<00:06:40.060> opinion<00:06:40.420> right<00:06:41.110> it's 00:06:41.310 --> 00:06:41.320 align:start position:0% political opinion right it's 00:06:41.320 --> 00:06:43.110 align:start position:0% political opinion right it's conventionally<00:06:41.800> a<00:06:41.830> question<00:06:42.370> because 00:06:43.110 --> 00:06:43.120 align:start position:0% conventionally a question because 00:06:43.120 --> 00:06:44.460 align:start position:0% conventionally a question because somebody<00:06:43.480> speaking<00:06:43.750> is<00:06:43.870> can<00:06:44.020> be<00:06:44.110> blown<00:06:44.290> into 00:06:44.460 --> 00:06:44.470 align:start position:0% somebody speaking is can be blown into 00:06:44.470 --> 00:06:46.680 align:start position:0% somebody speaking is can be blown into some<00:06:44.740> other<00:06:44.890> people<00:06:45.160> I<00:06:45.430> think<00:06:46.330> it's<00:06:46.540> super 00:06:46.680 --> 00:06:46.690 align:start position:0% some other people I think it's super 00:06:46.690 --> 00:06:48.750 align:start position:0% some other people I think it's super hard<00:06:47.020> crack<00:06:47.620> and<00:06:47.800> also<00:06:47.980> fake<00:06:48.220> for<00:06:48.430> you<00:06:48.580> may 00:06:48.750 --> 00:06:48.760 align:start position:0% hard crack and also fake for you may 00:06:48.760 --> 00:06:51.150 align:start position:0% hard crack and also fake for you may have<00:06:48.880> a<00:06:48.910> different<00:06:49.470> definition<00:06:50.470> than<00:06:50.830> for<00:06:51.070> me 00:06:51.150 --> 00:06:51.160 align:start position:0% have a different definition than for me 00:06:51.160 --> 00:06:53.580 align:start position:0% have a different definition than for me maybe<00:06:51.370> you<00:06:52.210> know<00:06:52.330> you<00:06:52.390> find<00:06:52.720> the<00:06:52.900> news<00:06:53.260> that<00:06:53.470> is 00:06:53.580 --> 00:06:53.590 align:start position:0% maybe you know you find the news that is 00:06:53.590 --> 00:06:56.010 align:start position:0% maybe you know you find the news that is so<00:06:53.740> fake<00:06:54.010> that<00:06:54.220> is<00:06:54.340> hilarious<00:06:55.000> right<00:06:55.180> versus<00:06:55.870> a 00:06:56.010 --> 00:06:56.020 align:start position:0% so fake that is hilarious right versus a 00:06:56.020 --> 00:06:58.560 align:start position:0% so fake that is hilarious right versus a lot<00:06:56.590> of<00:06:56.680> persons<00:06:57.040> say<00:06:57.340> in<00:06:57.640> the<00:06:57.760> midwives<00:06:58.180> or<00:06:58.480> in 00:06:58.560 --> 00:06:58.570 align:start position:0% lot of persons say in the midwives or in 00:06:58.570 --> 00:07:00.450 align:start position:0% lot of persons say in the midwives or in these<00:06:58.660> girls<00:06:58.990> will<00:06:59.200> get<00:06:59.620> offensive<00:06:59.890> that's 00:07:00.450 --> 00:07:00.460 align:start position:0% these girls will get offensive that's 00:07:00.460 --> 00:07:00.810 align:start position:0% these girls will get offensive that's right 00:07:00.810 --> 00:07:00.820 align:start position:0% right 00:07:00.820 --> 00:07:03.480 align:start position:0% right so<00:07:01.300> understanding<00:07:01.840> the<00:07:01.900> how<00:07:02.710> humans<00:07:03.370> will 00:07:03.480 --> 00:07:03.490 align:start position:0% so understanding the how humans will 00:07:03.490 --> 00:07:05.280 align:start position:0% so understanding the how humans will answer<00:07:03.700> to<00:07:04.150> the<00:07:04.270> question<00:07:04.600> is<00:07:04.720> this<00:07:04.840> fake<00:07:05.080> or 00:07:05.280 --> 00:07:05.290 align:start position:0% answer to the question is this fake or 00:07:05.290 --> 00:07:07.800 align:start position:0% answer to the question is this fake or not<00:07:05.470> it's<00:07:05.950> also<00:07:06.130> very<00:07:06.370> important<00:07:06.850> so<00:07:06.970> you'd 00:07:07.800 --> 00:07:07.810 align:start position:0% not it's also very important so you'd 00:07:07.810 --> 00:07:09.120 align:start position:0% not it's also very important so you'd never<00:07:07.990> have<00:07:08.170> to<00:07:08.200> take<00:07:08.380> it<00:07:08.530> for<00:07:08.650> granted<00:07:08.680> and 00:07:09.120 --> 00:07:09.130 align:start position:0% never have to take it for granted and 00:07:09.130 --> 00:07:11.250 align:start position:0% never have to take it for granted and say<00:07:09.280> oh<00:07:09.340> just<00:07:09.640> go<00:07:09.880> and<00:07:10.000> grab<00:07:10.540> some<00:07:10.630> fake<00:07:11.050> news 00:07:11.250 --> 00:07:11.260 align:start position:0% say oh just go and grab some fake news 00:07:11.260 --> 00:07:12.990 align:start position:0% say oh just go and grab some fake news data<00:07:11.470> set<00:07:11.710> because<00:07:12.310> there's<00:07:12.610> always<00:07:12.760> gonna<00:07:12.910> be 00:07:12.990 --> 00:07:13.000 align:start position:0% data set because there's always gonna be 00:07:13.000 --> 00:07:13.890 align:start position:0% data set because there's always gonna be very<00:07:13.300> difficult 00:07:13.890 --> 00:07:13.900 align:start position:0% very difficult 00:07:13.900 --> 00:07:16.470 align:start position:0% very difficult yeah<00:07:14.500> so<00:07:14.710> you<00:07:14.770> know<00:07:14.890> it's<00:07:15.100> so<00:07:15.640> like<00:07:15.970> that's<00:07:16.330> the 00:07:16.470 --> 00:07:16.480 align:start position:0% yeah so you know it's so like that's the 00:07:16.480 --> 00:07:18.030 align:start position:0% yeah so you know it's so like that's the ground<00:07:16.690> true<00:07:16.810> but<00:07:17.020> now<00:07:17.140> you<00:07:17.200> you<00:07:17.650> are<00:07:17.800> into 00:07:18.030 --> 00:07:18.040 align:start position:0% ground true but now you you are into 00:07:18.040 --> 00:07:18.690 align:start position:0% ground true but now you you are into knowledge<00:07:18.220> broths 00:07:18.690 --> 00:07:18.700 align:start position:0% knowledge broths 00:07:18.700 --> 00:07:20.850 align:start position:0% knowledge broths yeah<00:07:18.880> so<00:07:19.120> how<00:07:19.300> do<00:07:19.360> you<00:07:19.600> move<00:07:19.750> from<00:07:19.960> labels<00:07:20.440> to 00:07:20.850 --> 00:07:20.860 align:start position:0% yeah so how do you move from labels to 00:07:20.860 --> 00:07:24.390 align:start position:0% yeah so how do you move from labels to large<00:07:21.070> knowledge<00:07:21.430> drops<00:07:23.010> it's<00:07:24.010> an<00:07:24.130> internal 00:07:24.390 --> 00:07:24.400 align:start position:0% large knowledge drops it's an internal 00:07:24.400 --> 00:07:27.450 align:start position:0% large knowledge drops it's an internal project<00:07:24.700> so<00:07:25.120> I've<00:07:25.300> been<00:07:25.420> working<00:07:25.660> on<00:07:26.460> the 00:07:27.450 --> 00:07:27.460 align:start position:0% project so I've been working on the 00:07:27.460 --> 00:07:28.980 align:start position:0% project so I've been working on the reason<00:07:27.730> why<00:07:27.850> I<00:07:27.880> got<00:07:28.150> into<00:07:28.360> labels<00:07:28.510> is<00:07:28.780> to 00:07:28.980 --> 00:07:28.990 align:start position:0% reason why I got into labels is to 00:07:28.990 --> 00:07:30.990 align:start position:0% reason why I got into labels is to leverage<00:07:29.380> human<00:07:29.950> sensing<00:07:30.340> and<00:07:30.580> with<00:07:30.790> social 00:07:30.990 --> 00:07:31.000 align:start position:0% leverage human sensing and with social 00:07:31.000 --> 00:07:34.200 align:start position:0% leverage human sensing and with social data<00:07:31.390> say<00:07:32.230> Twitter<00:07:32.560> or<00:07:32.830> Facebook<00:07:33.520> there's<00:07:34.120> a 00:07:34.200 --> 00:07:34.210 align:start position:0% data say Twitter or Facebook there's a 00:07:34.210 --> 00:07:37.320 align:start position:0% data say Twitter or Facebook there's a lot<00:07:34.360> of<00:07:34.450> human<00:07:35.050> computation<00:07:35.410> at<00:07:35.650> scale<00:07:36.000> so<00:07:37.000> why 00:07:37.320 --> 00:07:37.330 align:start position:0% lot of human computation at scale so why 00:07:37.330 --> 00:07:39.270 align:start position:0% lot of human computation at scale so why not<00:07:37.480> just<00:07:37.840> deriving<00:07:38.260> graph<00:07:38.620> from<00:07:39.040> that 00:07:39.270 --> 00:07:39.280 align:start position:0% not just deriving graph from that 00:07:39.280 --> 00:07:41.190 align:start position:0% not just deriving graph from that sensing<00:07:39.760> mm-hmm<00:07:40.510> so<00:07:40.810> if<00:07:40.930> you've<00:07:41.050> already 00:07:41.190 --> 00:07:41.200 align:start position:0% sensing mm-hmm so if you've already 00:07:41.200 --> 00:07:44.130 align:start position:0% sensing mm-hmm so if you've already stood<00:07:41.830> in<00:07:41.980> today<00:07:42.420> instead<00:07:43.420> of<00:07:43.570> like<00:07:43.720> counting 00:07:44.130 --> 00:07:44.140 align:start position:0% stood in today instead of like counting 00:07:44.140 --> 00:07:46.110 align:start position:0% stood in today instead of like counting hashtags<00:07:44.620> and<00:07:44.860> through<00:07:45.010> the<00:07:45.070> topic<00:07:45.520> can<00:07:46.030> you 00:07:46.110 --> 00:07:46.120 align:start position:0% hashtags and through the topic can you 00:07:46.120 --> 00:07:48.690 align:start position:0% hashtags and through the topic can you derive<00:07:46.270> a<00:07:46.450> graph<00:07:46.840> if<00:07:47.800> you<00:07:47.860> have<00:07:48.220> a<00:07:48.250> lot<00:07:48.460> of<00:07:48.490> been 00:07:48.690 --> 00:07:48.700 align:start position:0% derive a graph if you have a lot of been 00:07:48.700 --> 00:07:50.820 align:start position:0% derive a graph if you have a lot of been sharing<00:07:49.180> with<00:07:49.210> veena<00:07:49.870> social<00:07:50.290> network<00:07:50.620> can 00:07:50.820 --> 00:07:50.830 align:start position:0% sharing with veena social network can 00:07:50.830 --> 00:07:53.450 align:start position:0% sharing with veena social network can you<00:07:50.950> derive<00:07:51.100> something<00:07:51.550> else<00:07:51.940> so<00:07:52.660> basically 00:07:53.450 --> 00:07:53.460 align:start position:0% you derive something else so basically 00:07:53.460 --> 00:07:55.440 align:start position:0% you derive something else so basically aggregations<00:07:54.460> that<00:07:54.610> you<00:07:54.670> can<00:07:54.820> do<00:07:55.000> that<00:07:55.360> are 00:07:55.440 --> 00:07:55.450 align:start position:0% aggregations that you can do that are 00:07:55.450 --> 00:07:56.820 align:start position:0% aggregations that you can do that are just<00:07:55.750> beyond<00:07:56.080> counting 00:07:56.820 --> 00:07:56.830 align:start position:0% just beyond counting 00:07:56.830 --> 00:07:59.250 align:start position:0% just beyond counting terms<00:07:57.370> or<00:07:57.790> topics<00:07:58.150> but<00:07:58.720> if<00:07:58.810> you<00:07:58.900> can<00:07:59.050> derive 00:07:59.250 --> 00:07:59.260 align:start position:0% terms or topics but if you can derive 00:07:59.260 --> 00:08:01.620 align:start position:0% terms or topics but if you can derive these<00:07:59.560> connections<00:08:00.190> has<00:08:01.030> a<00:08:01.060> lot<00:08:01.270> of<00:08:01.300> labeling 00:08:01.620 --> 00:08:01.630 align:start position:0% these connections has a lot of labeling 00:08:01.630 --> 00:08:03.900 align:start position:0% these connections has a lot of labeling yes<00:08:02.200> Raven<00:08:02.770> is<00:08:02.920> also<00:08:03.190> hard<00:08:03.400> because<00:08:03.580> now<00:08:03.850> you 00:08:03.900 --> 00:08:03.910 align:start position:0% yes Raven is also hard because now you 00:08:03.910 --> 00:08:05.540 align:start position:0% yes Raven is also hard because now you have<00:08:04.090> to<00:08:04.210> label<00:08:04.510> the<00:08:04.630> quality<00:08:05.020> of<00:08:05.110> the<00:08:05.200> graphs 00:08:05.540 --> 00:08:05.550 align:start position:0% have to label the quality of the graphs 00:08:05.550 --> 00:08:08.340 align:start position:0% have to label the quality of the graphs but<00:08:06.550> it's<00:08:06.730> kind<00:08:07.000> of<00:08:07.060> like<00:08:07.120> the<00:08:07.540> next<00:08:07.660> step<00:08:08.020> on 00:08:08.340 --> 00:08:08.350 align:start position:0% but it's kind of like the next step on 00:08:08.350 --> 00:08:11.010 align:start position:0% but it's kind of like the next step on on<00:08:08.800> labeling<00:08:09.160> from<00:08:09.940> my<00:08:10.060> perspective<00:08:10.360> in<00:08:10.900> my 00:08:11.010 --> 00:08:11.020 align:start position:0% on labeling from my perspective in my 00:08:11.020 --> 00:08:13.260 align:start position:0% on labeling from my perspective in my own<00:08:11.590> products<00:08:12.130> I<00:08:12.280> just<00:08:12.520> say<00:08:12.580> so<00:08:12.970> knowledge 00:08:13.260 --> 00:08:13.270 align:start position:0% own products I just say so knowledge 00:08:13.270 --> 00:08:15.450 align:start position:0% own products I just say so knowledge graphs<00:08:13.510> is<00:08:13.690> an<00:08:14.230> established<00:08:14.740> area<00:08:15.040> right<00:08:15.280> and 00:08:15.450 --> 00:08:15.460 align:start position:0% graphs is an established area right and 00:08:15.460 --> 00:08:17.880 align:start position:0% graphs is an established area right and so<00:08:15.580> on<00:08:15.640> and<00:08:15.940> if<00:08:16.030> in<00:08:16.120> my<00:08:16.270> mind<00:08:16.600> it<00:08:17.230> was<00:08:17.410> like<00:08:17.440> the 00:08:17.880 --> 00:08:17.890 align:start position:0% so on and if in my mind it was like the 00:08:17.890 --> 00:08:19.490 align:start position:0% so on and if in my mind it was like the what<00:08:18.100> comes<00:08:18.280> to<00:08:18.430> mind<00:08:18.550> the<00:08:18.670> meters<00:08:18.910> are<00:08:19.060> DF<00:08:19.390> and 00:08:19.490 --> 00:08:19.500 align:start position:0% what comes to mind the meters are DF and 00:08:19.500 --> 00:08:22.620 align:start position:0% what comes to mind the meters are DF and Semantic<00:08:20.500> Web<00:08:20.530> yes<00:08:21.160> and<00:08:21.400> it's<00:08:21.850> kind<00:08:22.210> of<00:08:22.300> it<00:08:22.450> was 00:08:22.620 --> 00:08:22.630 align:start position:0% Semantic Web yes and it's kind of it was 00:08:22.630 --> 00:08:25.260 align:start position:0% Semantic Web yes and it's kind of it was cool<00:08:23.050> for<00:08:23.080> some<00:08:23.680> time<00:08:23.950> yes<00:08:24.460> but<00:08:24.760> not<00:08:25.000> recently 00:08:25.260 --> 00:08:25.270 align:start position:0% cool for some time yes but not recently 00:08:25.270 --> 00:08:27.150 align:start position:0% cool for some time yes but not recently well<00:08:25.660> I<00:08:25.690> think<00:08:25.870> it<00:08:26.050> was<00:08:26.230> there<00:08:26.590> was<00:08:26.680> a<00:08:26.710> like 00:08:27.150 --> 00:08:27.160 align:start position:0% well I think it was there was a like 00:08:27.160 --> 00:08:29.400 align:start position:0% well I think it was there was a like it's<00:08:27.340> a<00:08:27.430> movie<00:08:27.700> before<00:08:27.910> I<00:08:28.120> die<00:08:28.330> before<00:08:29.110> I<00:08:29.230> kill 00:08:29.400 --> 00:08:29.410 align:start position:0% it's a movie before I die before I kill 00:08:29.410 --> 00:08:31.620 align:start position:0% it's a movie before I die before I kill mother<00:08:29.620> I'm<00:08:29.890> kind<00:08:30.190> of<00:08:30.250> fashionable<00:08:30.760> I<00:08:30.910> write 00:08:31.620 --> 00:08:31.630 align:start position:0% mother I'm kind of fashionable I write 00:08:31.630 --> 00:08:33.209 align:start position:0% mother I'm kind of fashionable I write there<00:08:31.900> was<00:08:32.050> a<00:08:32.080> notion<00:08:32.349> that<00:08:32.800> like<00:08:32.979> at<00:08:33.099> some 00:08:33.209 --> 00:08:33.219 align:start position:0% there was a notion that like at some 00:08:33.219 --> 00:08:35.640 align:start position:0% there was a notion that like at some point<00:08:33.250> it<00:08:33.580> looked<00:08:33.729> like<00:08:33.910> the<00:08:34.510> bill<00:08:35.200> Semantic 00:08:35.640 --> 00:08:35.650 align:start position:0% point it looked like the bill Semantic 00:08:35.650 --> 00:08:35.850 align:start position:0% point it looked like the bill Semantic Web 00:08:35.850 --> 00:08:35.860 align:start position:0% Web 00:08:35.860 --> 00:08:37.680 align:start position:0% Web everybody's<00:08:36.550> gonna<00:08:36.729> very<00:08:37.030> like 00:08:37.680 --> 00:08:37.690 align:start position:0% everybody's gonna very like 00:08:37.690 --> 00:08:40.430 align:start position:0% everybody's gonna very like painstakingly<00:08:38.410> underneath<00:08:38.890> their<00:08:39.190> website 00:08:40.430 --> 00:08:40.440 align:start position:0% painstakingly underneath their website 00:08:40.440 --> 00:08:42.740 align:start position:0% painstakingly underneath their website protocol<00:08:40.950> and<00:08:41.190> we'll<00:08:41.340> be<00:08:41.460> semantic<00:08:41.880> triples 00:08:42.740 --> 00:08:42.750 align:start position:0% protocol and we'll be semantic triples 00:08:42.750 --> 00:08:45.200 align:start position:0% protocol and we'll be semantic triples everywhere<00:08:43.289> and<00:08:43.590> didn't<00:08:43.979> materialize<00:08:44.670> like 00:08:45.200 --> 00:08:45.210 align:start position:0% everywhere and didn't materialize like 00:08:45.210 --> 00:08:47.510 align:start position:0% everywhere and didn't materialize like it's<00:08:45.330> really<00:08:45.660> I<00:08:45.900> think<00:08:46.680> the<00:08:46.860> feeling<00:08:47.070> like 00:08:47.510 --> 00:08:47.520 align:start position:0% it's really I think the feeling like 00:08:47.520 --> 00:08:49.250 align:start position:0% it's really I think the feeling like there<00:08:47.880> are<00:08:47.940> some<00:08:48.060> like<00:08:48.480> hardcore<00:08:48.750> veterans 00:08:49.250 --> 00:08:49.260 align:start position:0% there are some like hardcore veterans 00:08:49.260 --> 00:08:52.910 align:start position:0% there are some like hardcore veterans who<00:08:49.440> still<00:08:50.040> do<00:08:50.160> that<00:08:50.340> right<00:08:51.060> and<00:08:51.390> I<00:08:52.290> feel<00:08:52.770> like 00:08:52.910 --> 00:08:52.920 align:start position:0% who still do that right and I feel like 00:08:52.920 --> 00:08:55.010 align:start position:0% who still do that right and I feel like I've<00:08:53.070> seen<00:08:53.610> a<00:08:53.670> lot<00:08:53.820> of<00:08:54.000> work<00:08:54.300> from<00:08:54.600> German 00:08:55.010 --> 00:08:55.020 align:start position:0% I've seen a lot of work from German 00:08:55.020 --> 00:08:56.930 align:start position:0% I've seen a lot of work from German universities<00:08:55.590> and<00:08:56.010> I<00:08:56.100> think<00:08:56.280> I<00:08:56.370> can<00:08:56.580> see<00:08:56.910> my 00:08:56.930 --> 00:08:56.940 align:start position:0% universities and I think I can see my 00:08:56.940 --> 00:09:00.080 align:start position:0% universities and I think I can see my catalog<00:08:57.390> and<00:08:57.510> everything<00:08:57.900> but<00:08:58.560> but<00:08:58.970> where<00:08:59.970> is 00:09:00.080 --> 00:09:00.090 align:start position:0% catalog and everything but but where is 00:09:00.090 --> 00:09:01.610 align:start position:0% catalog and everything but but where is this<00:09:00.240> field<00:09:00.570> I'd<00:09:00.840> like<00:09:01.020> and<00:09:01.170> I<00:09:01.230> met<00:09:01.440> people 00:09:01.610 --> 00:09:01.620 align:start position:0% this field I'd like and I met people 00:09:01.620 --> 00:09:02.570 align:start position:0% this field I'd like and I met people from<00:09:01.740> Google 00:09:02.570 --> 00:09:02.580 align:start position:0% from Google 00:09:02.580 --> 00:09:04.370 align:start position:0% from Google I<00:09:02.610> think<00:09:03.360> Eugene<00:09:03.630> Gabriel<00:09:03.900> of<00:09:04.020> which<00:09:04.170> was 00:09:04.370 --> 00:09:04.380 align:start position:0% I think Eugene Gabriel of which was 00:09:04.380 --> 00:09:07.160 align:start position:0% I think Eugene Gabriel of which was knowledge<00:09:05.340> graphs<00:09:05.610> right<00:09:05.790> so<00:09:05.970> but<00:09:06.510> I<00:09:06.750> think 00:09:07.160 --> 00:09:07.170 align:start position:0% knowledge graphs right so but I think 00:09:07.170 --> 00:09:08.480 align:start position:0% knowledge graphs right so but I think they<00:09:07.260> didn't<00:09:07.470> like<00:09:07.500> it<00:09:07.620> internally<00:09:08.310> to<00:09:08.370> do 00:09:08.480 --> 00:09:08.490 align:start position:0% they didn't like it internally to do 00:09:08.490 --> 00:09:12.260 align:start position:0% they didn't like it internally to do some<00:09:08.900> modeling<00:09:09.900> so<00:09:10.410> but<00:09:10.560> I<00:09:10.770> don't<00:09:11.070> see<00:09:11.550> you 00:09:12.260 --> 00:09:12.270 align:start position:0% some modeling so but I don't see you 00:09:12.270 --> 00:09:14.930 align:start position:0% some modeling so but I don't see you know<00:09:12.450> like<00:09:13.110> mainstream<00:09:13.710> companies<00:09:14.280> talking<00:09:14.790> a 00:09:14.930 --> 00:09:14.940 align:start position:0% know like mainstream companies talking a 00:09:14.940 --> 00:09:16.940 align:start position:0% know like mainstream companies talking a lot<00:09:15.150> about<00:09:15.180> it<00:09:15.630> like<00:09:15.810> what<00:09:15.990> is<00:09:16.350> it<00:09:16.560> is<00:09:16.680> this 00:09:16.940 --> 00:09:16.950 align:start position:0% lot about it like what is it is this 00:09:16.950 --> 00:09:21.620 align:start position:0% lot about it like what is it is this still<00:09:17.580> a<00:09:18.480> very<00:09:18.900> like<00:09:20.000> but<00:09:21.000> I<00:09:21.030> know<00:09:21.180> it's<00:09:21.420> used 00:09:21.620 --> 00:09:21.630 align:start position:0% still a very like but I know it's used 00:09:21.630 --> 00:09:23.030 align:start position:0% still a very like but I know it's used internally<00:09:22.080> I<00:09:22.230> just<00:09:22.380> don't<00:09:22.710> know<00:09:22.800> how<00:09:22.980> much 00:09:23.030 --> 00:09:23.040 align:start position:0% internally I just don't know how much 00:09:23.040 --> 00:09:25.100 align:start position:0% internally I just don't know how much with<00:09:23.280> this<00:09:23.370> proprietary<00:09:23.670> how<00:09:24.630> much<00:09:24.840> of<00:09:24.960> it<00:09:25.080> is 00:09:25.100 --> 00:09:25.110 align:start position:0% with this proprietary how much of it is 00:09:25.110 --> 00:09:27.770 align:start position:0% with this proprietary how much of it is you<00:09:25.560> know<00:09:25.590> open<00:09:26.430> research<00:09:26.790> like<00:09:27.240> what's<00:09:27.630> the 00:09:27.770 --> 00:09:27.780 align:start position:0% you know open research like what's the 00:09:27.780 --> 00:09:30.980 align:start position:0% you know open research like what's the state<00:09:27.990> of<00:09:28.140> knowledge<00:09:28.320> graphs<00:09:29.540> great<00:09:30.540> question 00:09:30.980 --> 00:09:30.990 align:start position:0% state of knowledge graphs great question 00:09:30.990 --> 00:09:32.630 align:start position:0% state of knowledge graphs great question so<00:09:31.170> our<00:09:31.350> approach<00:09:31.830> to<00:09:32.070> knowledge<00:09:32.220> graph<00:09:32.520> is 00:09:32.630 --> 00:09:32.640 align:start position:0% so our approach to knowledge graph is 00:09:32.640 --> 00:09:34.940 align:start position:0% so our approach to knowledge graph is not<00:09:32.970> the<00:09:33.270> traditional<00:09:33.480> AI<00:09:34.050> what<00:09:34.620> you<00:09:34.770> just 00:09:34.940 --> 00:09:34.950 align:start position:0% not the traditional AI what you just 00:09:34.950 --> 00:09:36.860 align:start position:0% not the traditional AI what you just mentioned<00:09:35.250> it's<00:09:36.060> basically<00:09:36.360> more<00:09:36.630> like 00:09:36.860 --> 00:09:36.870 align:start position:0% mentioned it's basically more like 00:09:36.870 --> 00:09:40.490 align:start position:0% mentioned it's basically more like domain-specific<00:09:37.970> graphs<00:09:39.140> which<00:09:40.140> have<00:09:40.350> some 00:09:40.490 --> 00:09:40.500 align:start position:0% domain-specific graphs which have some 00:09:40.500 --> 00:09:42.760 align:start position:0% domain-specific graphs which have some knowledge<00:09:40.680> on<00:09:41.610> it 00:09:42.760 --> 00:09:42.770 align:start position:0% knowledge on it 00:09:42.770 --> 00:09:45.710 align:start position:0% knowledge on it you<00:09:43.770> mentioned<00:09:44.160> Eugene<00:09:44.700> who<00:09:44.970> is<00:09:45.120> at<00:09:45.300> Google 00:09:45.710 --> 00:09:45.720 align:start position:0% you mentioned Eugene who is at Google 00:09:45.720 --> 00:09:47.810 align:start position:0% you mentioned Eugene who is at Google Google<00:09:46.110> has<00:09:46.230> has<00:09:46.650> this<00:09:46.860> Google<00:09:47.670> knowledge 00:09:47.810 --> 00:09:47.820 align:start position:0% Google has has this Google knowledge 00:09:47.820 --> 00:09:48.110 align:start position:0% Google has has this Google knowledge graph 00:09:48.110 --> 00:09:48.120 align:start position:0% graph 00:09:48.120 --> 00:09:49.940 align:start position:0% graph Microsoft<00:09:48.780> has<00:09:48.900> the<00:09:49.050> Satori<00:09:49.380> knowledge<00:09:49.680> graph 00:09:49.940 --> 00:09:49.950 align:start position:0% Microsoft has the Satori knowledge graph 00:09:49.950 --> 00:09:52.100 align:start position:0% Microsoft has the Satori knowledge graph another<00:09:50.760> companies<00:09:51.300> like<00:09:51.510> Amazon<00:09:51.960> they're 00:09:52.100 --> 00:09:52.110 align:start position:0% another companies like Amazon they're 00:09:52.110 --> 00:09:53.360 align:start position:0% another companies like Amazon they're willing<00:09:52.320> in<00:09:52.440> all<00:09:52.590> knowledge<00:09:52.890> graph<00:09:53.130> for 00:09:53.360 --> 00:09:53.370 align:start position:0% willing in all knowledge graph for 00:09:53.370 --> 00:09:55.880 align:start position:0% willing in all knowledge graph for products<00:09:54.200> Pinterest<00:09:55.200> is<00:09:55.290> also<00:09:55.530> building<00:09:55.800> a 00:09:55.880 --> 00:09:55.890 align:start position:0% products Pinterest is also building a 00:09:55.890 --> 00:09:57.320 align:start position:0% products Pinterest is also building a knowledge<00:09:56.220> graph<00:09:56.370> for<00:09:56.700> red<00:09:56.850> across<00:09:57.120> the 00:09:57.320 --> 00:09:57.330 align:start position:0% knowledge graph for red across the 00:09:57.330 --> 00:10:00.610 align:start position:0% knowledge graph for red across the street<00:09:57.540> so<00:09:57.990> you<00:09:58.350> can<00:09:58.500> think<00:09:58.620> of<00:09:58.800> like<00:09:58.920> little 00:10:00.610 --> 00:10:00.620 align:start position:0% street so you can think of like little 00:10:00.620 --> 00:10:03.800 align:start position:0% street so you can think of like little little<00:10:01.620> graphs<00:10:01.890> that<00:10:02.280> are<00:10:02.640> specific<00:10:03.540> for<00:10:03.570> the 00:10:03.800 --> 00:10:03.810 align:start position:0% little graphs that are specific for the 00:10:03.810 --> 00:10:06.620 align:start position:0% little graphs that are specific for the domains<00:10:04.160> entertainment<00:10:05.160> business<00:10:05.730> etc<00:10:06.240> so 00:10:06.620 --> 00:10:06.630 align:start position:0% domains entertainment business etc so 00:10:06.630 --> 00:10:08.630 align:start position:0% domains entertainment business etc so the<00:10:06.750> goal<00:10:06.870> here<00:10:06.900> is<00:10:07.140> not<00:10:07.170> to<00:10:07.320> capture<00:10:07.650> the 00:10:08.630 --> 00:10:08.640 align:start position:0% the goal here is not to capture the 00:10:08.640 --> 00:10:11.600 align:start position:0% the goal here is not to capture the world<00:10:08.850> view<00:10:09.060> so<00:10:09.870> that<00:10:09.900> we<00:10:10.140> cannot<00:10:10.530> the<00:10:10.740> psyche 00:10:11.600 --> 00:10:11.610 align:start position:0% world view so that we cannot the psyche 00:10:11.610 --> 00:10:13.580 align:start position:0% world view so that we cannot the psyche and<00:10:12.060> all<00:10:12.210> those<00:10:12.390> projects<00:10:12.870> but<00:10:13.110> it's<00:10:13.410> more 00:10:13.580 --> 00:10:13.590 align:start position:0% and all those projects but it's more 00:10:13.590 --> 00:10:16.940 align:start position:0% and all those projects but it's more like<00:10:13.940> for<00:10:14.940> a<00:10:14.970> specific<00:10:15.330> domain<00:10:15.840> say<00:10:16.320> music<00:10:16.770> you 00:10:16.940 --> 00:10:16.950 align:start position:0% like for a specific domain say music you 00:10:16.950 --> 00:10:18.380 align:start position:0% like for a specific domain say music you know<00:10:17.070> who<00:10:17.280> are<00:10:17.340> the<00:10:17.460> black<00:10:17.670> what<00:10:18.090> the<00:10:18.210> bands 00:10:18.380 --> 00:10:18.390 align:start position:0% know who are the black what the bands 00:10:18.390 --> 00:10:20.630 align:start position:0% know who are the black what the bands were<00:10:18.600> the<00:10:18.750> players<00:10:18.990> were<00:10:19.260> the<00:10:19.410> genre<00:10:19.890> etc<00:10:20.490> and 00:10:20.630 --> 00:10:20.640 align:start position:0% were the players were the genre etc and 00:10:20.640 --> 00:10:22.610 align:start position:0% were the players were the genre etc and have<00:10:20.820> all<00:10:21.000> these<00:10:21.150> connections<00:10:21.720> if<00:10:22.140> possible 00:10:22.610 --> 00:10:22.620 align:start position:0% have all these connections if possible 00:10:22.620 --> 00:10:25.310 align:start position:0% have all these connections if possible automatically<00:10:23.400> derive<00:10:23.700> mmm<00:10:24.480> so<00:10:25.050> it's<00:10:25.170> not 00:10:25.310 --> 00:10:25.320 align:start position:0% automatically derive mmm so it's not 00:10:25.320 --> 00:10:27.079 align:start position:0% automatically derive mmm so it's not it's<00:10:25.500> more<00:10:25.680> about<00:10:26.040> a<00:10:26.339> data-driven<00:10:26.640> approach 00:10:27.079 --> 00:10:27.089 align:start position:0% it's more about a data-driven approach 00:10:27.089 --> 00:10:30.950 align:start position:0% it's more about a data-driven approach to<00:10:27.600> detect<00:10:28.440> entities<00:10:29.000> entity<00:10:30.000> resolution<00:10:30.180> and 00:10:30.950 --> 00:10:30.960 align:start position:0% to detect entities entity resolution and 00:10:30.960 --> 00:10:31.700 align:start position:0% to detect entities entity resolution and linkage 00:10:31.700 --> 00:10:31.710 align:start position:0% linkage 00:10:31.710 --> 00:10:35.360 align:start position:0% linkage etc<00:10:32.370> then<00:10:32.970> you<00:10:33.000> can<00:10:33.180> expose<00:10:33.510> us<00:10:33.720> a<00:10:33.750> graph<00:10:34.370> with 00:10:35.360 --> 00:10:35.370 align:start position:0% etc then you can expose us a graph with 00:10:35.370 --> 00:10:36.740 align:start position:0% etc then you can expose us a graph with annotation<00:10:35.970> so<00:10:36.060> you<00:10:36.150> can<00:10:36.270> color<00:10:36.450> knowledge 00:10:36.740 --> 00:10:36.750 align:start position:0% annotation so you can color knowledge 00:10:36.750 --> 00:10:38.570 align:start position:0% annotation so you can color knowledge graph<00:10:36.960> that's<00:10:37.140> how<00:10:37.230> we<00:10:37.290> call<00:10:37.530> it<00:10:37.589> it's<00:10:38.400> not 00:10:38.570 --> 00:10:38.580 align:start position:0% graph that's how we call it it's not 00:10:38.580 --> 00:10:41.300 align:start position:0% graph that's how we call it it's not like<00:10:38.850> a<00:10:38.880> super<00:10:39.330> you<00:10:40.290> know<00:10:40.410> the<00:10:40.770> world<00:10:40.980> view<00:10:41.190> of 00:10:41.300 --> 00:10:41.310 align:start position:0% like a super you know the world view of 00:10:41.310 --> 00:10:41.780 align:start position:0% like a super you know the world view of although 00:10:41.780 --> 00:10:41.790 align:start position:0% although 00:10:41.790 --> 00:10:43.820 align:start position:0% although or<00:10:42.120> the<00:10:42.270> planet<00:10:42.660> but<00:10:42.839> it's<00:10:42.990> a<00:10:43.200> good 00:10:43.820 --> 00:10:43.830 align:start position:0% or the planet but it's a good 00:10:43.830 --> 00:10:45.680 align:start position:0% or the planet but it's a good representation<00:10:44.280> of<00:10:44.760> a<00:10:44.880> specific<00:10:45.360> domain 00:10:45.680 --> 00:10:45.690 align:start position:0% representation of a specific domain 00:10:45.690 --> 00:10:49.379 align:start position:0% representation of a specific domain interesting<00:10:46.350> so<00:10:47.010> this<00:10:47.160> comes<00:10:47.490> from 00:10:49.379 --> 00:10:49.389 align:start position:0% interesting so this comes from 00:10:49.389 --> 00:10:52.870 align:start position:0% interesting so this comes from original<00:10:51.100> questionnaires<00:10:52.100> or<00:10:52.370> is<00:10:52.519> it<00:10:52.639> derived 00:10:52.870 --> 00:10:52.880 align:start position:0% original questionnaires or is it derived 00:10:52.880 --> 00:10:54.340 align:start position:0% original questionnaires or is it derived automatically<00:10:53.449> like<00:10:53.540> what<00:10:53.690> do<00:10:53.810> we<00:10:53.930> need<00:10:54.110> from 00:10:54.340 --> 00:10:54.350 align:start position:0% automatically like what do we need from 00:10:54.350 --> 00:10:57.069 align:start position:0% automatically like what do we need from humans<00:10:54.709> the<00:10:55.399> levels<00:10:55.730> of<00:10:55.820> human<00:10:56.120> rights<00:10:56.839> in<00:10:57.050> the 00:10:57.069 --> 00:10:57.079 align:start position:0% humans the levels of human rights in the 00:10:57.079 --> 00:11:00.160 align:start position:0% humans the levels of human rights in the case<00:10:57.440> of<00:10:57.709> the<00:10:58.540> teskigi<00:10:59.540> graph<00:10:59.870> that<00:11:00.019> will 00:11:00.160 --> 00:11:00.170 align:start position:0% case of the teskigi graph that will 00:11:00.170 --> 00:11:02.680 align:start position:0% case of the teskigi graph that will we'll<00:11:00.680> talk<00:11:01.070> today<00:11:01.250> is<00:11:01.639> about<00:11:02.029> detecting 00:11:02.680 --> 00:11:02.690 align:start position:0% we'll talk today is about detecting 00:11:02.690 --> 00:11:09.310 align:start position:0% we'll talk today is about detecting links<00:11:03.850> people<00:11:05.079> topics<00:11:07.839> detect<00:11:08.839> that<00:11:08.959> and<00:11:09.139> make 00:11:09.310 --> 00:11:09.320 align:start position:0% links people topics detect that and make 00:11:09.320 --> 00:11:11.530 align:start position:0% links people topics detect that and make a<00:11:09.350> few<00:11:09.620> connections<00:11:09.920> you<00:11:10.760> can<00:11:10.910> build<00:11:11.149> some<00:11:11.360> pre 00:11:11.530 --> 00:11:11.540 align:start position:0% a few connections you can build some pre 00:11:11.540 --> 00:11:13.449 align:start position:0% a few connections you can build some pre interesting<00:11:11.930> applications<00:11:12.560> you<00:11:13.160> don't<00:11:13.279> have 00:11:13.449 --> 00:11:13.459 align:start position:0% interesting applications you don't have 00:11:13.459 --> 00:11:15.370 align:start position:0% interesting applications you don't have to<00:11:13.550> have<00:11:13.730> you<00:11:14.000> don't<00:11:14.149> have<00:11:14.240> to<00:11:14.329> go<00:11:14.449> full<00:11:15.050> fledge 00:11:15.370 --> 00:11:15.380 align:start position:0% to have you don't have to go full fledge 00:11:15.380 --> 00:11:19.139 align:start position:0% to have you don't have to go full fledge into<00:11:16.120> super<00:11:17.120> crazy<00:11:17.360> techniques<00:11:18.230> which<00:11:18.829> is 00:11:19.139 --> 00:11:19.149 align:start position:0% into super crazy techniques which is 00:11:19.149 --> 00:11:21.069 align:start position:0% into super crazy techniques which is understanding<00:11:20.149> people<00:11:20.660> places 00:11:21.069 --> 00:11:21.079 align:start position:0% understanding people places 00:11:21.079 --> 00:11:23.829 align:start position:0% understanding people places organizations<00:11:21.860> links<00:11:22.399> topics<00:11:23.240> and<00:11:23.510> then<00:11:23.630> make 00:11:23.829 --> 00:11:23.839 align:start position:0% organizations links topics and then make 00:11:23.839 --> 00:11:25.810 align:start position:0% organizations links topics and then make the<00:11:23.959> connections<00:11:24.470> the<00:11:24.920> occurrences<00:11:25.639> or 00:11:25.810 --> 00:11:25.820 align:start position:0% the connections the occurrences or 00:11:25.820 --> 00:11:27.790 align:start position:0% the connections the occurrences or anything<00:11:26.089> else<00:11:26.329> and<00:11:26.990> you<00:11:27.139> can<00:11:27.260> have<00:11:27.380> a<00:11:27.440> pre 00:11:27.790 --> 00:11:27.800 align:start position:0% anything else and you can have a pre 00:11:27.800 --> 00:11:32.079 align:start position:0% anything else and you can have a pre decent<00:11:28.250> graph<00:11:29.120> I<00:11:30.079> say<00:11:30.800> graph<00:11:31.010> we<00:11:31.790> could<00:11:31.940> call 00:11:32.079 --> 00:11:32.089 align:start position:0% decent graph I say graph we could call 00:11:32.089 --> 00:11:33.250 align:start position:0% decent graph I say graph we could call it<00:11:32.209> knowledge<00:11:32.360> graph<00:11:32.630> because<00:11:32.899> have<00:11:33.050> some 00:11:33.250 --> 00:11:33.260 align:start position:0% it knowledge graph because have some 00:11:33.260 --> 00:11:36.670 align:start position:0% it knowledge graph because have some knowledge<00:11:33.500> in<00:11:33.769> it<00:11:33.920> but<00:11:34.339> it's<00:11:34.490> not<00:11:34.790> RDF<00:11:35.750> and<00:11:36.440> we 00:11:36.670 --> 00:11:36.680 align:start position:0% knowledge in it but it's not RDF and we 00:11:36.680 --> 00:11:38.199 align:start position:0% knowledge in it but it's not RDF and we don't<00:11:36.860> know<00:11:37.010> we<00:11:37.250> already<00:11:37.399> care<00:11:37.820> on<00:11:38.000> the 00:11:38.199 --> 00:11:38.209 align:start position:0% don't know we already care on the 00:11:38.209 --> 00:11:40.150 align:start position:0% don't know we already care on the representation<00:11:39.050> of<00:11:39.170> it<00:11:39.290> it's<00:11:39.470> mostly<00:11:39.889> like 00:11:40.150 --> 00:11:40.160 align:start position:0% representation of it it's mostly like 00:11:40.160 --> 00:11:42.790 align:start position:0% representation of it it's mostly like which<00:11:41.120> are<00:11:41.269> the<00:11:41.389> different<00:11:41.720> entry<00:11:42.380> points<00:11:42.410> you 00:11:42.790 --> 00:11:42.800 align:start position:0% which are the different entry points you 00:11:42.800 --> 00:11:44.740 align:start position:0% which are the different entry points you can<00:11:42.949> choreograph<00:11:43.190> and<00:11:43.760> get<00:11:44.000> data<00:11:44.180> around<00:11:44.570> it 00:11:44.740 --> 00:11:44.750 align:start position:0% can choreograph and get data around it 00:11:44.750 --> 00:11:47.199 align:start position:0% can choreograph and get data around it that<00:11:44.959> before<00:11:45.139> was<00:11:45.529> difficult<00:11:46.070> in<00:11:46.670> the<00:11:46.820> example 00:11:47.199 --> 00:11:47.209 align:start position:0% that before was difficult in the example 00:11:47.209 --> 00:11:50.079 align:start position:0% that before was difficult in the example of<00:11:47.389> Twitter<00:11:48.100> you<00:11:49.100> can<00:11:49.220> see<00:11:49.459> what<00:11:49.639> people<00:11:49.910> say 00:11:50.079 --> 00:11:50.089 align:start position:0% of Twitter you can see what people say 00:11:50.089 --> 00:11:52.060 align:start position:0% of Twitter you can see what people say so<00:11:50.149> for<00:11:50.540> the<00:11:50.690> u.s.<00:11:50.930> elections<00:11:51.350> two<00:11:51.589> years<00:11:51.829> ago 00:11:52.060 --> 00:11:52.070 align:start position:0% so for the u.s. elections two years ago 00:11:52.070 --> 00:11:53.800 align:start position:0% so for the u.s. elections two years ago before<00:11:52.310> the<00:11:52.550> u.s.<00:11:52.670> elections<00:11:53.120> which<00:11:53.690> is 00:11:53.800 --> 00:11:53.810 align:start position:0% before the u.s. elections which is 00:11:53.810 --> 00:11:55.150 align:start position:0% before the u.s. elections which is something<00:11:54.079> is<00:11:54.170> difficult<00:11:54.589> to<00:11:54.649> see<00:11:54.800> today<00:11:54.949> in 00:11:55.150 --> 00:11:55.160 align:start position:0% something is difficult to see today in 00:11:55.160 --> 00:11:58.389 align:start position:0% something is difficult to see today in to<00:11:55.310> her<00:11:56.560> this<00:11:57.560> is<00:11:57.620> just<00:11:57.920> my<00:11:58.040> brother<00:11:58.220> these 00:11:58.389 --> 00:11:58.399 align:start position:0% to her this is just my brother these 00:11:58.399 --> 00:12:01.449 align:start position:0% to her this is just my brother these little<00:11:58.790> little<00:11:59.149> artifacts<00:12:00.160> you<00:12:01.160> see 00:12:01.449 --> 00:12:01.459 align:start position:0% little little artifacts you see 00:12:01.459 --> 00:12:02.889 align:start position:0% little little artifacts you see interesting<00:12:02.149> so<00:12:02.510> it's<00:12:02.690> kind<00:12:02.839> of 00:12:02.889 --> 00:12:02.899 align:start position:0% interesting so it's kind of 00:12:02.899 --> 00:12:04.509 align:start position:0% interesting so it's kind of domain-specific<00:12:03.230> knowledge<00:12:03.920> drops 00:12:04.509 --> 00:12:04.519 align:start position:0% domain-specific knowledge drops 00:12:04.519 --> 00:12:07.240 align:start position:0% domain-specific knowledge drops domain-specific<00:12:05.480> knowledge<00:12:05.959> wrap<00:12:06.350> perhaps 00:12:07.240 --> 00:12:07.250 align:start position:0% domain-specific knowledge wrap perhaps 00:12:07.250 --> 00:12:09.960 align:start position:0% domain-specific knowledge wrap perhaps is<00:12:07.399> a<00:12:07.430> better<00:12:07.519> it's<00:12:08.089> a<00:12:08.209> better<00:12:08.480> terminology<00:12:09.230> is 00:12:09.960 --> 00:12:09.970 align:start position:0% is a better it's a better terminology is 00:12:09.970 --> 00:12:12.040 align:start position:0% is a better it's a better terminology is lightweight<00:12:10.970> that<00:12:11.480> let's<00:12:11.660> put<00:12:11.779> it<00:12:11.839> this<00:12:11.899> way 00:12:12.040 --> 00:12:12.050 align:start position:0% lightweight that let's put it this way 00:12:12.050 --> 00:12:16.019 align:start position:0% lightweight that let's put it this way lightweight<00:12:12.529> cavies<00:12:13.449> which<00:12:14.449> are<00:12:14.600> not<00:12:14.899> super 00:12:16.019 --> 00:12:16.029 align:start position:0% lightweight cavies which are not super 00:12:16.029 --> 00:12:19.449 align:start position:0% lightweight cavies which are not super comprehensive<00:12:17.029> I<00:12:17.180> mean<00:12:17.480> for<00:12:17.810> the<00:12:18.160> for<00:12:19.160> at<00:12:19.370> an 00:12:19.449 --> 00:12:19.459 align:start position:0% comprehensive I mean for the for at an 00:12:19.459 --> 00:12:21.639 align:start position:0% comprehensive I mean for the for at an encyclopedia<00:12:19.819> like<00:12:20.269> Wikipedia<00:12:20.810> but<00:12:21.500> it's 00:12:21.639 --> 00:12:21.649 align:start position:0% encyclopedia like Wikipedia but it's 00:12:21.649 --> 00:12:22.870 align:start position:0% encyclopedia like Wikipedia but it's very<00:12:21.800> good<00:12:22.069> at<00:12:22.190> the<00:12:22.339> domain 00:12:22.870 --> 00:12:22.880 align:start position:0% very good at the domain 00:12:22.880 --> 00:12:25.840 align:start position:0% very good at the domain unlike<00:12:23.360> hierarchical<00:12:23.990> or<00:12:24.199> other<00:12:24.350> flat<00:12:24.850> people 00:12:25.840 --> 00:12:25.850 align:start position:0% unlike hierarchical or other flat people 00:12:25.850 --> 00:12:28.960 align:start position:0% unlike hierarchical or other flat people on<00:12:25.940> topic<00:12:26.300> so<00:12:26.449> this<00:12:26.810> is<00:12:26.959> one<00:12:27.110> level<00:12:27.970> hierarchy 00:12:28.960 --> 00:12:28.970 align:start position:0% on topic so this is one level hierarchy 00:12:28.970 --> 00:12:32.530 align:start position:0% on topic so this is one level hierarchy of<00:12:29.300> topics<00:12:29.630> well<00:12:30.170> which<00:12:30.380> we<00:12:30.589> feel<00:12:31.329> so<00:12:32.329> for<00:12:32.480> the 00:12:32.530 --> 00:12:32.540 align:start position:0% of topics well which we feel so for the 00:12:32.540 --> 00:12:34.930 align:start position:0% of topics well which we feel so for the one<00:12:32.660> that<00:12:32.779> 1%<00:12:33.019> we<00:12:33.350> don't<00:12:33.529> but<00:12:34.100> if<00:12:34.220> you<00:12:34.370> if<00:12:34.699> you 00:12:34.930 --> 00:12:34.940 align:start position:0% one that 1% we don't but if you if you 00:12:34.940 --> 00:12:37.720 align:start position:0% one that 1% we don't but if you if you have<00:12:35.269> the<00:12:35.480> baseline<00:12:35.930> well<00:12:36.829> done<00:12:37.069> then 00:12:37.720 --> 00:12:37.730 align:start position:0% have the baseline well done then 00:12:37.730 --> 00:12:39.189 align:start position:0% have the baseline well done then aggregations<00:12:38.240> are<00:12:38.360> somewhat<00:12:38.750> easy<00:12:38.899> to 00:12:39.189 --> 00:12:39.199 align:start position:0% aggregations are somewhat easy to 00:12:39.199 --> 00:12:41.470 align:start position:0% aggregations are somewhat easy to develop<00:12:39.980> and<00:12:40.160> we'll<00:12:40.370> show<00:12:40.579> also<00:12:40.880> a<00:12:41.060> couple<00:12:41.389> of 00:12:41.470 --> 00:12:41.480 align:start position:0% develop and we'll show also a couple of 00:12:41.480 --> 00:12:43.569 align:start position:0% develop and we'll show also a couple of examples<00:12:41.899> on<00:12:42.050> those<00:12:42.230> aggregations<00:12:42.889> which<00:12:43.459> is 00:12:43.569 --> 00:12:43.579 align:start position:0% examples on those aggregations which is 00:12:43.579 --> 00:12:44.980 align:start position:0% examples on those aggregations which is that<00:12:43.699> the<00:12:43.970> the<00:12:44.180> point<00:12:44.420> of<00:12:44.600> villanies 00:12:44.980 --> 00:12:44.990 align:start position:0% that the the point of villanies 00:12:44.990 --> 00:12:46.870 align:start position:0% that the the point of villanies domain-specific<00:12:45.829> knowledge<00:12:46.310> graph<00:12:46.639> it's 00:12:46.870 --> 00:12:46.880 align:start position:0% domain-specific knowledge graph it's 00:12:46.880 --> 00:12:48.300 align:start position:0% domain-specific knowledge graph it's like<00:12:47.089> the<00:12:47.240> aggregation<00:12:47.690> that<00:12:47.720> you<00:12:47.870> can<00:12:47.990> build 00:12:48.300 --> 00:12:48.310 align:start position:0% like the aggregation that you can build 00:12:48.310 --> 00:12:52.090 align:start position:0% like the aggregation that you can build so<00:12:49.310> it's<00:12:49.399> not<00:12:49.579> about<00:12:49.790> the<00:12:50.500> data<00:12:51.500> information 00:12:52.090 --> 00:12:52.100 align:start position:0% so it's not about the data information 00:12:52.100 --> 00:12:54.460 align:start position:0% so it's not about the data information knowledge<00:12:52.459> so<00:12:53.180> that<00:12:53.209> pyramid<00:12:53.839> is<00:12:53.930> mostly<00:12:54.260> like 00:12:54.460 --> 00:12:54.470 align:start position:0% knowledge so that pyramid is mostly like 00:12:54.470 --> 00:12:55.840 align:start position:0% knowledge so that pyramid is mostly like if<00:12:54.769> you<00:12:54.920> have<00:12:55.069> these<00:12:55.220> little<00:12:55.550> connections 00:12:55.840 --> 00:12:55.850 align:start position:0% if you have these little connections 00:12:55.850 --> 00:12:58.090 align:start position:0% if you have these little connections what<00:12:56.300> can<00:12:56.449> you<00:12:56.540> do<00:12:56.750> versus<00:12:57.560> I<00:12:57.680> don't<00:12:57.860> have<00:12:57.980> the 00:12:58.090 --> 00:12:58.100 align:start position:0% what can you do versus I don't have the 00:12:58.100 --> 00:12:59.530 align:start position:0% what can you do versus I don't have the connections<00:12:58.579> therefore<00:12:58.939> it's<00:12:59.060> difficult<00:12:59.449> to 00:12:59.530 --> 00:12:59.540 align:start position:0% connections therefore it's difficult to 00:12:59.540 --> 00:13:01.600 align:start position:0% connections therefore it's difficult to do<00:12:59.660> this<00:12:59.839> mmm-hmm<00:13:00.439> interesting<00:13:01.069> so<00:13:01.220> I<00:13:01.399> wasn't 00:13:01.600 --> 00:13:01.610 align:start position:0% do this mmm-hmm interesting so I wasn't 00:13:01.610 --> 00:13:02.400 align:start position:0% do this mmm-hmm interesting so I wasn't gonna<00:13:01.760> shoot 00:13:02.400 --> 00:13:02.410 align:start position:0% gonna shoot 00:13:02.410 --> 00:13:04.530 align:start position:0% gonna shoot a little<00:13:02.649> bit<00:13:02.769> in<00:13:03.180> sense<00:13:04.180> the<00:13:04.360> maybe 00:13:04.530 --> 00:13:04.540 align:start position:0% a little bit in sense the maybe 00:13:04.540 --> 00:13:06.900 align:start position:0% a little bit in sense the maybe connection<00:13:05.079> maybe<00:13:05.290> not<00:13:05.529> but<00:13:05.680> let's<00:13:05.889> see<00:13:06.040> so<00:13:06.550> so 00:13:06.900 --> 00:13:06.910 align:start position:0% connection maybe not but let's see so so 00:13:06.910 --> 00:13:08.309 align:start position:0% connection maybe not but let's see so so I<00:13:06.940> took<00:13:07.149> to<00:13:07.269> for<00:13:07.420> a<00:13:07.449> socialite<00:13:07.870> who's<00:13:08.170> the 00:13:08.309 --> 00:13:08.319 align:start position:0% I took to for a socialite who's the 00:13:08.319 --> 00:13:10.920 align:start position:0% I took to for a socialite who's the Kira's<00:13:08.649> creator<00:13:09.639> he's<00:13:10.029> at<00:13:10.149> Google<00:13:10.480> and<00:13:10.690> he's<00:13:10.839> a 00:13:10.920 --> 00:13:10.930 align:start position:0% Kira's creator he's at Google and he's a 00:13:10.930 --> 00:13:12.990 align:start position:0% Kira's creator he's at Google and he's a Google<00:13:11.230> brain<00:13:11.410> right<00:13:11.860> and<00:13:12.069> I<00:13:12.190> talked<00:13:12.519> to<00:13:12.759> him 00:13:12.990 --> 00:13:13.000 align:start position:0% Google brain right and I talked to him 00:13:13.000 --> 00:13:16.259 align:start position:0% Google brain right and I talked to him about<00:13:13.089> deep<00:13:13.959> learning<00:13:14.940> beginning<00:13:15.940> of<00:13:16.060> this 00:13:16.259 --> 00:13:16.269 align:start position:0% about deep learning beginning of this 00:13:16.269 --> 00:13:19.110 align:start position:0% about deep learning beginning of this year<00:13:16.690> last<00:13:16.959> year<00:13:17.079> which<00:13:17.620> was<00:13:17.800> like<00:13:17.980> the<00:13:18.129> peak 00:13:19.110 --> 00:13:19.120 align:start position:0% year last year which was like the peak 00:13:19.120 --> 00:13:21.119 align:start position:0% year last year which was like the peak of<00:13:19.389> kind<00:13:20.079> of<00:13:20.170> deep<00:13:20.560> yearning<00:13:20.680> is<00:13:20.860> gonna<00:13:20.980> solve 00:13:21.119 --> 00:13:21.129 align:start position:0% of kind of deep yearning is gonna solve 00:13:21.129 --> 00:13:23.550 align:start position:0% of kind of deep yearning is gonna solve everything<00:13:21.310> right<00:13:22.089> so<00:13:22.209> basically<00:13:22.509> and<00:13:23.050> he<00:13:23.410> was 00:13:23.550 --> 00:13:23.560 align:start position:0% everything right so basically and he was 00:13:23.560 --> 00:13:24.990 align:start position:0% everything right so basically and he was very<00:13:23.709> interested<00:13:23.980> in<00:13:24.189> the<00:13:24.310> key<00:13:24.519> he<00:13:24.730> kind<00:13:24.939> of 00:13:24.990 --> 00:13:25.000 align:start position:0% very interested in the key he kind of 00:13:25.000 --> 00:13:28.129 align:start position:0% very interested in the key he kind of was<00:13:25.180> saying<00:13:25.930> that<00:13:26.290> deploring<00:13:26.860> will<00:13:27.189> never<00:13:27.370> be 00:13:28.129 --> 00:13:28.139 align:start position:0% was saying that deploring will never be 00:13:28.139 --> 00:13:30.600 align:start position:0% was saying that deploring will never be general<00:13:29.139> artificial<00:13:29.800> intelligence<00:13:30.339> in 00:13:30.600 --> 00:13:30.610 align:start position:0% general artificial intelligence in 00:13:30.610 --> 00:13:32.550 align:start position:0% general artificial intelligence in Mexico<00:13:30.939> saying<00:13:31.209> it<00:13:31.509> will<00:13:31.720> it's<00:13:32.170> not<00:13:32.230> capable 00:13:32.550 --> 00:13:32.560 align:start position:0% Mexico saying it will it's not capable 00:13:32.560 --> 00:13:35.189 align:start position:0% Mexico saying it will it's not capable of<00:13:33.009> generalization<00:13:33.819> because<00:13:34.420> it's<00:13:34.750> very<00:13:35.019> good 00:13:35.189 --> 00:13:35.199 align:start position:0% of generalization because it's very good 00:13:35.199 --> 00:13:37.559 align:start position:0% of generalization because it's very good with<00:13:35.439> pattern<00:13:35.860> detection<00:13:36.160> right<00:13:37.120> but<00:13:37.329> it<00:13:37.480> will 00:13:37.559 --> 00:13:37.569 align:start position:0% with pattern detection right but it will 00:13:37.569 --> 00:13:39.240 align:start position:0% with pattern detection right but it will not<00:13:37.720> generalize<00:13:38.319> like<00:13:38.709> if<00:13:38.829> it<00:13:38.980> give<00:13:39.160> you 00:13:39.240 --> 00:13:39.250 align:start position:0% not generalize like if it give you 00:13:39.250 --> 00:13:41.220 align:start position:0% not generalize like if it give you different<00:13:39.430> kind<00:13:39.879> of<00:13:39.970> some<00:13:40.360> different<00:13:40.959> kind<00:13:41.199> of 00:13:41.220 --> 00:13:41.230 align:start position:0% different kind of some different kind of 00:13:41.230 --> 00:13:43.350 align:start position:0% different kind of some different kind of stripes<00:13:41.620> if<00:13:42.100> you<00:13:42.459> give<00:13:42.610> it<00:13:42.699> a<00:13:42.759> completely<00:13:43.209> new 00:13:43.350 --> 00:13:43.360 align:start position:0% stripes if you give it a completely new 00:13:43.360 --> 00:13:45.569 align:start position:0% stripes if you give it a completely new kind<00:13:43.540> of<00:13:43.689> stripes<00:13:44.019> I<00:13:44.170> shall<00:13:44.319> not<00:13:44.500> you<00:13:44.680> know<00:13:44.829> the 00:13:45.569 --> 00:13:45.579 align:start position:0% kind of stripes I shall not you know the 00:13:45.579 --> 00:13:47.939 align:start position:0% kind of stripes I shall not you know the kind<00:13:45.759> of<00:13:45.819> so<00:13:46.029> it<00:13:46.120> will<00:13:46.269> not<00:13:46.589> understand<00:13:47.589> it<00:13:47.740> and 00:13:47.939 --> 00:13:47.949 align:start position:0% kind of so it will not understand it and 00:13:47.949 --> 00:13:50.220 align:start position:0% kind of so it will not understand it and so<00:13:47.980> he<00:13:48.550> was<00:13:48.699> actually<00:13:48.819> talking<00:13:49.509> about<00:13:49.569> that<00:13:49.779> we 00:13:50.220 --> 00:13:50.230 align:start position:0% so he was actually talking about that we 00:13:50.230 --> 00:13:53.040 align:start position:0% so he was actually talking about that we need<00:13:50.379> a<00:13:50.410> fusion<00:13:50.980> of<00:13:51.480> statistical<00:13:52.480> AI<00:13:52.720> and 00:13:53.040 --> 00:13:53.050 align:start position:0% need a fusion of statistical AI and 00:13:53.050 --> 00:13:55.889 align:start position:0% need a fusion of statistical AI and logically<00:13:53.740> I<00:13:53.769> and<00:13:54.610> I<00:13:54.759> think<00:13:54.970> through<00:13:55.420> Russel 00:13:55.889 --> 00:13:55.899 align:start position:0% logically I and I think through Russel 00:13:55.899 --> 00:13:57.660 align:start position:0% logically I and I think through Russel Berger<00:13:56.500> talked<00:13:56.860> about<00:13:57.100> that<00:13:57.279> as<00:13:57.430> well<00:13:57.579> so 00:13:57.660 --> 00:13:57.670 align:start position:0% Berger talked about that as well so 00:13:57.670 --> 00:13:59.790 align:start position:0% Berger talked about that as well so basically<00:13:57.790> that<00:13:58.660> like<00:13:58.959> the<00:13:59.110> hinting<00:13:59.500> at<00:13:59.649> this 00:13:59.790 --> 00:13:59.800 align:start position:0% basically that like the hinting at this 00:13:59.800 --> 00:14:02.429 align:start position:0% basically that like the hinting at this like<00:14:00.069> the<00:14:00.310> limit<00:14:01.180> of<00:14:01.269> statistical<00:14:01.899> AI<00:14:02.110> which 00:14:02.429 --> 00:14:02.439 align:start position:0% like the limit of statistical AI which 00:14:02.439 --> 00:14:03.540 align:start position:0% like the limit of statistical AI which we<00:14:02.560> are<00:14:02.620> doing<00:14:03.009> right<00:14:03.160> now 00:14:03.540 --> 00:14:03.550 align:start position:0% we are doing right now 00:14:03.550 --> 00:14:06.569 align:start position:0% we are doing right now and<00:14:03.850> they<00:14:04.689> needs<00:14:04.899> to<00:14:05.110> be<00:14:05.290> some<00:14:05.709> combination 00:14:06.569 --> 00:14:06.579 align:start position:0% and they needs to be some combination 00:14:06.579 --> 00:14:10.009 align:start position:0% and they needs to be some combination with<00:14:07.509> what<00:14:08.110> you<00:14:08.259> know<00:14:08.380> cool<00:14:09.100> used<00:14:09.550> to<00:14:09.610> be<00:14:09.699> cool 00:14:10.009 --> 00:14:10.019 align:start position:0% with what you know cool used to be cool 00:14:10.019 --> 00:14:12.660 align:start position:0% with what you know cool used to be cool traditionally<00:14:11.019> I<00:14:11.050> right<00:14:11.860> so<00:14:12.130> we've<00:14:12.459> got<00:14:12.579> this 00:14:12.660 --> 00:14:12.670 align:start position:0% traditionally I right so we've got this 00:14:12.670 --> 00:14:14.280 align:start position:0% traditionally I right so we've got this knowledge<00:14:13.000> basis<00:14:13.360> or<00:14:13.480> something<00:14:13.509> else<00:14:13.899> but 00:14:14.280 --> 00:14:14.290 align:start position:0% knowledge basis or something else but 00:14:14.290 --> 00:14:16.350 align:start position:0% knowledge basis or something else but basically<00:14:14.709> like<00:14:15.100> I<00:14:15.430> was<00:14:15.699> surprised<00:14:16.029> to<00:14:16.149> find 00:14:16.350 --> 00:14:16.360 align:start position:0% basically like I was surprised to find 00:14:16.360 --> 00:14:18.960 align:start position:0% basically like I was surprised to find you<00:14:16.990> know<00:14:17.110> among<00:14:18.009> the<00:14:18.160> kind<00:14:18.339> of<00:14:18.399> cutting-edge 00:14:18.960 --> 00:14:18.970 align:start position:0% you know among the kind of cutting-edge 00:14:18.970 --> 00:14:20.939 align:start position:0% you know among the kind of cutting-edge people<00:14:19.360> and<00:14:19.630> deploring<00:14:20.050> the<00:14:20.079> feeling<00:14:20.769> that 00:14:20.939 --> 00:14:20.949 align:start position:0% people and deploring the feeling that 00:14:20.949 --> 00:14:22.470 align:start position:0% people and deploring the feeling that you<00:14:21.220> know<00:14:21.339> you<00:14:21.399> need<00:14:21.639> something<00:14:21.970> else<00:14:22.089> to<00:14:22.329> go 00:14:22.470 --> 00:14:22.480 align:start position:0% you know you need something else to go 00:14:22.480 --> 00:14:25.949 align:start position:0% you know you need something else to go to<00:14:23.259> the<00:14:23.350> next<00:14:23.589> level<00:14:23.889> and<00:14:24.130> and<00:14:24.730> so<00:14:25.000> I<00:14:25.449> wonder 00:14:25.949 --> 00:14:25.959 align:start position:0% to the next level and and so I wonder 00:14:25.959 --> 00:14:28.470 align:start position:0% to the next level and and so I wonder like<00:14:26.050> the<00:14:26.620> work<00:14:27.009> you<00:14:27.040> do<00:14:27.370> kind<00:14:27.699> of<00:14:27.759> is<00:14:28.029> it<00:14:28.240> kind 00:14:28.470 --> 00:14:28.480 align:start position:0% like the work you do kind of is it kind 00:14:28.480 --> 00:14:30.960 align:start position:0% like the work you do kind of is it kind of<00:14:28.569> the<00:14:28.660> kind<00:14:29.139> of<00:14:29.230> related<00:14:29.949> can<00:14:30.130> it<00:14:30.250> be<00:14:30.430> an 00:14:30.960 --> 00:14:30.970 align:start position:0% of the kind of related can it be an 00:14:30.970 --> 00:14:33.569 align:start position:0% of the kind of related can it be an automatic<00:14:31.560> like<00:14:32.560> building<00:14:32.860> knowledge<00:14:33.130> bases 00:14:33.569 --> 00:14:33.579 align:start position:0% automatic like building knowledge bases 00:14:33.579 --> 00:14:35.280 align:start position:0% automatic like building knowledge bases like<00:14:34.120> basically<00:14:34.509> we<00:14:34.660> need<00:14:34.779> world<00:14:34.959> knowledge 00:14:35.280 --> 00:14:35.290 align:start position:0% like basically we need world knowledge 00:14:35.290 --> 00:14:36.749 align:start position:0% like basically we need world knowledge in<00:14:35.439> some<00:14:35.620> way<00:14:35.769> we<00:14:35.980> need<00:14:36.130> something<00:14:36.370> else<00:14:36.490> and 00:14:36.749 --> 00:14:36.759 align:start position:0% in some way we need something else and 00:14:36.759 --> 00:14:41.220 align:start position:0% in some way we need something else and besides<00:14:37.720> deep<00:14:37.930> learning<00:14:38.189> is<00:14:39.189> this<00:14:40.230> possible 00:14:41.220 --> 00:14:41.230 align:start position:0% besides deep learning is this possible 00:14:41.230 --> 00:14:43.620 align:start position:0% besides deep learning is this possible complement<00:14:41.860> to<00:14:42.130> deep<00:14:42.459> learning<00:14:42.639> or<00:14:43.060> it's<00:14:43.389> it's 00:14:43.620 --> 00:14:43.630 align:start position:0% complement to deep learning or it's it's 00:14:43.630 --> 00:14:46.439 align:start position:0% complement to deep learning or it's it's its<00:14:43.930> own<00:14:44.139> kind<00:14:44.589> of<00:14:44.819> specialized<00:14:45.819> area<00:14:46.209> do<00:14:46.360> you 00:14:46.439 --> 00:14:46.449 align:start position:0% its own kind of specialized area do you 00:14:46.449 --> 00:14:49.980 align:start position:0% its own kind of specialized area do you see<00:14:46.689> any<00:14:47.339> interaction<00:14:48.339> so<00:14:49.269> for<00:14:49.480> the<00:14:49.600> record<00:14:49.899> I 00:14:49.980 --> 00:14:49.990 align:start position:0% see any interaction so for the record I 00:14:49.990 --> 00:14:51.059 align:start position:0% see any interaction so for the record I don't<00:14:50.199> know<00:14:50.290> anything<00:14:50.500> about<00:14:50.680> deep<00:14:50.889> learning 00:14:51.059 --> 00:14:51.069 align:start position:0% don't know anything about deep learning 00:14:51.069 --> 00:14:54.780 align:start position:0% don't know anything about deep learning so<00:14:51.519> can't<00:14:52.149> comment<00:14:52.420> on<00:14:52.660> that<00:14:52.899> front<00:14:53.519> there<00:14:54.519> one 00:14:54.780 --> 00:14:54.790 align:start position:0% so can't comment on that front there one 00:14:54.790 --> 00:14:56.280 align:start position:0% so can't comment on that front there one of<00:14:54.819> the<00:14:54.910> reasons<00:14:55.269> why<00:14:55.449> we've<00:14:55.689> done<00:14:56.019> this 00:14:56.280 --> 00:14:56.290 align:start position:0% of the reasons why we've done this 00:14:56.290 --> 00:14:59.189 align:start position:0% of the reasons why we've done this bottom-up<00:14:57.130> and<00:14:57.370> supervised<00:14:57.819> is<00:14:58.569> going<00:14:59.019> back 00:14:59.189 --> 00:14:59.199 align:start position:0% bottom-up and supervised is going back 00:14:59.199 --> 00:15:01.139 align:start position:0% bottom-up and supervised is going back to<00:14:59.410> one<00:14:59.649> of<00:14:59.740> the<00:14:59.829> other<00:15:00.189> points<00:15:00.610> you<00:15:00.819> were 00:15:01.139 --> 00:15:01.149 align:start position:0% to one of the other points you were 00:15:01.149 --> 00:15:03.420 align:start position:0% to one of the other points you were mentioning<00:15:01.540> is<00:15:02.019> about<00:15:02.290> explained<00:15:02.680> ability<00:15:03.129> so 00:15:03.420 --> 00:15:03.430 align:start position:0% mentioning is about explained ability so 00:15:03.430 --> 00:15:06.569 align:start position:0% mentioning is about explained ability so if<00:15:03.519> you<00:15:03.610> want<00:15:03.879> to<00:15:04.259> the<00:15:05.259> tag<00:15:05.529> that<00:15:05.769> Alexia<00:15:06.309> it<00:15:06.399> is 00:15:06.569 --> 00:15:06.579 align:start position:0% if you want to the tag that Alexia it is 00:15:06.579 --> 00:15:09.190 align:start position:0% if you want to the tag that Alexia it is you<00:15:07.029> know<00:15:07.180> related<00:15:07.959> to<00:15:08.199> say<00:15:08.410> dominoes 00:15:09.190 --> 00:15:09.200 align:start position:0% you know related to say dominoes 00:15:09.200 --> 00:15:11.560 align:start position:0% you know related to say dominoes so<00:15:09.380> something<00:15:09.860> how<00:15:10.700> can<00:15:10.730> you<00:15:10.940> explain<00:15:11.269> those 00:15:11.560 --> 00:15:11.570 align:start position:0% so something how can you explain those 00:15:11.570 --> 00:15:13.840 align:start position:0% so something how can you explain those relationships<00:15:12.350> and<00:15:12.560> sometimes<00:15:12.860> a<00:15:13.220> bottom-up 00:15:13.840 --> 00:15:13.850 align:start position:0% relationships and sometimes a bottom-up 00:15:13.850 --> 00:15:15.850 align:start position:0% relationships and sometimes a bottom-up approach<00:15:14.060> and<00:15:14.570> I<00:15:14.630> supervise<00:15:15.079> you<00:15:15.290> can<00:15:15.440> explain 00:15:15.850 --> 00:15:15.860 align:start position:0% approach and I supervise you can explain 00:15:15.860 --> 00:15:16.780 align:start position:0% approach and I supervise you can explain some<00:15:16.100> of<00:15:16.130> these<00:15:16.310> things 00:15:16.780 --> 00:15:16.790 align:start position:0% some of these things 00:15:16.790 --> 00:15:19.569 align:start position:0% some of these things mm-hmm<00:15:17.269> that's<00:15:17.389> one<00:15:17.839> of<00:15:17.930> the<00:15:17.990> reasons<00:15:18.350> why<00:15:18.579> the 00:15:19.569 --> 00:15:19.579 align:start position:0% mm-hmm that's one of the reasons why the 00:15:19.579 --> 00:15:21.190 align:start position:0% mm-hmm that's one of the reasons why the project<00:15:19.970> that<00:15:20.089> I'll<00:15:20.209> show<00:15:20.420> today<00:15:20.720> or<00:15:20.959> on 00:15:21.190 --> 00:15:21.200 align:start position:0% project that I'll show today or on 00:15:21.200 --> 00:15:24.310 align:start position:0% project that I'll show today or on Twitter<00:15:21.470> is<00:15:22.329> because<00:15:23.329> we<00:15:23.450> want<00:15:23.630> to<00:15:23.720> be<00:15:24.139> able<00:15:24.200> to 00:15:24.310 --> 00:15:24.320 align:start position:0% Twitter is because we want to be able to 00:15:24.320 --> 00:15:26.800 align:start position:0% Twitter is because we want to be able to explain<00:15:24.769> why<00:15:25.040> this<00:15:25.100> thing<00:15:25.399> is<00:15:26.000> related<00:15:26.570> to 00:15:26.800 --> 00:15:26.810 align:start position:0% explain why this thing is related to 00:15:26.810 --> 00:15:29.490 align:start position:0% explain why this thing is related to that<00:15:27.019> and<00:15:27.290> the<00:15:27.410> other<00:15:27.440> thing<00:15:27.769> is<00:15:28.389> provenance 00:15:29.490 --> 00:15:29.500 align:start position:0% that and the other thing is provenance 00:15:29.500 --> 00:15:32.710 align:start position:0% that and the other thing is provenance we<00:15:30.500> want<00:15:30.649> to<00:15:30.709> show<00:15:30.829> evidence<00:15:31.240> that<00:15:32.240> these<00:15:32.510> two 00:15:32.710 --> 00:15:32.720 align:start position:0% we want to show evidence that these two 00:15:32.720 --> 00:15:35.410 align:start position:0% we want to show evidence that these two things<00:15:32.750> are<00:15:33.079> related<00:15:33.139> and<00:15:33.860> if<00:15:34.820> you<00:15:35.269> can 00:15:35.410 --> 00:15:35.420 align:start position:0% things are related and if you can 00:15:35.420 --> 00:15:37.030 align:start position:0% things are related and if you can sprinkle<00:15:36.170> that<00:15:36.500> they<00:15:36.560> are<00:15:36.620> set<00:15:36.860> with 00:15:37.030 --> 00:15:37.040 align:start position:0% sprinkle that they are set with 00:15:37.040 --> 00:15:38.769 align:start position:0% sprinkle that they are set with provenance<00:15:37.550> which<00:15:37.639> is<00:15:37.940> a<00:15:37.970> well<00:15:38.600> understood 00:15:38.769 --> 00:15:38.779 align:start position:0% provenance which is a well understood 00:15:38.779 --> 00:15:41.290 align:start position:0% provenance which is a well understood topic<00:15:39.440> and<00:15:39.589> databases<00:15:39.949> then<00:15:40.880> you<00:15:41.000> can<00:15:41.149> make 00:15:41.290 --> 00:15:41.300 align:start position:0% topic and databases then you can make 00:15:41.300 --> 00:15:43.720 align:start position:0% topic and databases then you can make sense<00:15:41.510> of<00:15:41.720> this<00:15:42.010> pursuit<00:15:43.010> of<00:15:43.160> you<00:15:43.459> know<00:15:43.579> this 00:15:43.720 --> 00:15:43.730 align:start position:0% sense of this pursuit of you know this 00:15:43.730 --> 00:15:46.480 align:start position:0% sense of this pursuit of you know this thing<00:15:43.940> is<00:15:44.149> related<00:15:44.329> because<00:15:44.690> it's<00:15:45.199> magic<00:15:45.740> will 00:15:46.480 --> 00:15:46.490 align:start position:0% thing is related because it's magic will 00:15:46.490 --> 00:15:48.610 align:start position:0% thing is related because it's magic will be<00:15:46.610> its<00:15:46.790> ability<00:15:46.880> because<00:15:47.510> here's<00:15:48.230> what<00:15:48.440> we 00:15:48.610 --> 00:15:48.620 align:start position:0% be its ability because here's what we 00:15:48.620 --> 00:15:52.150 align:start position:0% be its ability because here's what we believe<00:15:48.889> it's<00:15:49.070> a<00:15:49.190> relationship<00:15:51.160> slightly 00:15:52.150 --> 00:15:52.160 align:start position:0% believe it's a relationship slightly 00:15:52.160 --> 00:15:54.160 align:start position:0% believe it's a relationship slightly maybe<00:15:52.550> there's<00:15:52.820> a<00:15:52.880> connection<00:15:53.120> I<00:15:53.449> I<00:15:53.600> don't 00:15:54.160 --> 00:15:54.170 align:start position:0% maybe there's a connection I I don't 00:15:54.170 --> 00:15:57.129 align:start position:0% maybe there's a connection I I don't know<00:15:54.529> this<00:15:54.860> one<00:15:55.100> is<00:15:55.660> bottom<00:15:56.660> out<00:15:56.779> that's<00:15:57.019> what 00:15:57.129 --> 00:15:57.139 align:start position:0% know this one is bottom out that's what 00:15:57.139 --> 00:15:57.939 align:start position:0% know this one is bottom out that's what I'm<00:15:57.230> trying<00:15:57.440> to<00:15:57.500> explain 00:15:57.939 --> 00:15:57.949 align:start position:0% I'm trying to explain 00:15:57.949 --> 00:15:59.560 align:start position:0% I'm trying to explain I<00:15:58.010> supervise<00:15:58.579> I'm<00:15:58.880> from<00:15:59.089> the<00:15:59.209> ground<00:15:59.389> up 00:15:59.560 --> 00:15:59.570 align:start position:0% I supervise I'm from the ground up 00:15:59.570 --> 00:16:01.420 align:start position:0% I supervise I'm from the ground up grassroots<00:16:00.170> if<00:16:00.350> you<00:16:00.440> want<00:16:00.589> to<00:16:00.680> call<00:16:00.800> it<00:16:00.949> mhm 00:16:01.420 --> 00:16:01.430 align:start position:0% grassroots if you want to call it mhm 00:16:01.430 --> 00:16:04.720 align:start position:0% grassroots if you want to call it mhm kind<00:16:02.180> of<00:16:02.269> a<00:16:02.300> lightweight<00:16:03.070> KB's<00:16:04.070> interesting 00:16:04.720 --> 00:16:04.730 align:start position:0% kind of a lightweight KB's interesting 00:16:04.730 --> 00:16:08.069 align:start position:0% kind of a lightweight KB's interesting yeah<00:16:05.149> I'll<00:16:05.329> let<00:16:05.480> our<00:16:05.660> viewers<00:16:05.930> further 00:16:08.069 --> 00:16:08.079 align:start position:0% yeah I'll let our viewers further 00:16:08.079 --> 00:16:15.699 align:start position:0% yeah I'll let our viewers further comment<00:16:11.410> when<00:16:12.410> they<00:16:12.560> see<00:16:12.740> it<00:16:12.829> cool<00:16:13.550> so<00:16:13.850> so<00:16:14.709> well 00:16:15.699 --> 00:16:15.709 align:start position:0% comment when they see it cool so so well 00:16:15.709 --> 00:16:17.170 align:start position:0% comment when they see it cool so so well definite<00:16:16.279> looking<00:16:16.490> forward<00:16:16.760> to<00:16:16.850> talk<00:16:17.089> about 00:16:17.170 --> 00:16:17.180 align:start position:0% definite looking forward to talk about 00:16:17.180 --> 00:16:19.569 align:start position:0% definite looking forward to talk about like<00:16:17.390> overall<00:16:18.010> where<00:16:19.010> is<00:16:19.220> your<00:16:19.370> research 00:16:19.569 --> 00:16:19.579 align:start position:0% like overall where is your research 00:16:19.579 --> 00:16:20.980 align:start position:0% like overall where is your research going<00:16:19.640> and<00:16:20.269> like<00:16:20.390> what<00:16:20.540> are<00:16:20.600> your<00:16:20.690> plans<00:16:20.839> for 00:16:20.980 --> 00:16:20.990 align:start position:0% going and like what are your plans for 00:16:20.990 --> 00:16:26.439 align:start position:0% going and like what are your plans for this<00:16:21.140> year<00:16:23.980> so<00:16:24.980> for<00:16:25.100> this<00:16:25.250> year<00:16:25.579> that<00:16:25.610> was 00:16:26.439 --> 00:16:26.449 align:start position:0% this year so for this year that was 00:16:26.449 --> 00:16:27.730 align:start position:0% this year so for this year that was gonna<00:16:26.570> be<00:16:26.720> here<00:16:26.959> in<00:16:27.050> San<00:16:27.290> Francisco 00:16:27.730 --> 00:16:27.740 align:start position:0% gonna be here in San Francisco 00:16:27.740 --> 00:16:30.579 align:start position:0% gonna be here in San Francisco mm-hmm<00:16:28.310> in<00:16:28.790> May<00:16:29.120> I'm<00:16:30.079> running<00:16:30.440> with 00:16:30.579 --> 00:16:30.589 align:start position:0% mm-hmm in May I'm running with 00:16:30.589 --> 00:16:33.189 align:start position:0% mm-hmm in May I'm running with co-chairing<00:16:31.519> we<00:16:31.730> love<00:16:32.240> the<00:16:32.600> human 00:16:33.189 --> 00:16:33.199 align:start position:0% co-chairing we love the human 00:16:33.199 --> 00:16:34.990 align:start position:0% co-chairing we love the human computation<00:16:33.709> track<00:16:34.130> which<00:16:34.490> we<00:16:34.670> have<00:16:34.790> some 00:16:34.990 --> 00:16:35.000 align:start position:0% computation track which we have some 00:16:35.000 --> 00:16:38.410 align:start position:0% computation track which we have some superb<00:16:35.899> papers<00:16:36.290> the<00:16:37.220> conference<00:16:37.610> is<00:16:38.209> going<00:16:38.329> to 00:16:38.410 --> 00:16:38.420 align:start position:0% superb papers the conference is going to 00:16:38.420 --> 00:16:41.069 align:start position:0% superb papers the conference is going to be<00:16:38.510> massive<00:16:38.920> so<00:16:39.920> if<00:16:40.339> you<00:16:40.459> can<00:16:40.579> attend<00:16:40.880> please 00:16:41.069 --> 00:16:41.079 align:start position:0% be massive so if you can attend please 00:16:41.079 --> 00:16:45.579 align:start position:0% be massive so if you can attend please attend<00:16:42.820> in<00:16:43.820> October<00:16:44.240> helping<00:16:45.230> out<00:16:45.320> with<00:16:45.440> H 00:16:45.579 --> 00:16:45.589 align:start position:0% attend in October helping out with H 00:16:45.589 --> 00:16:50.199 align:start position:0% attend in October helping out with H comp<00:16:45.890> the<00:16:46.220> human<00:16:46.490> computation<00:16:46.699> covers<00:16:49.209> near 00:16:50.199 --> 00:16:50.209 align:start position:0% comp the human computation covers near 00:16:50.209 --> 00:16:52.720 align:start position:0% comp the human computation covers near the<00:16:50.329> border<00:16:50.600> watching<00:16:51.079> Tuesday<00:16:51.500> the<00:16:52.339> rest<00:16:52.579> we 00:16:52.720 --> 00:16:52.730 align:start position:0% the border watching Tuesday the rest we 00:16:52.730 --> 00:16:54.790 align:start position:0% the border watching Tuesday the rest we have<00:16:52.760> a<00:16:52.910> few<00:16:53.149> things<00:16:53.420> or<00:16:53.930> nons<00:16:54.260> graphs<00:16:54.560> that<00:16:54.649> we 00:16:54.790 --> 00:16:54.800 align:start position:0% have a few things or nons graphs that we 00:16:54.800 --> 00:16:56.710 align:start position:0% have a few things or nons graphs that we would<00:16:54.920> like<00:16:55.040> to<00:16:55.190> if<00:16:55.550> we<00:16:55.790> get<00:16:56.209> a<00:16:56.240> forward<00:16:56.569> for 00:16:56.710 --> 00:16:56.720 align:start position:0% would like to if we get a forward for 00:16:56.720 --> 00:16:59.829 align:start position:0% would like to if we get a forward for Microsoft<00:16:57.199> to<00:16:57.319> publish<00:16:58.329> that's<00:16:59.329> it<00:16:59.510> we<00:16:59.660> mean 00:16:59.829 --> 00:16:59.839 align:start position:0% Microsoft to publish that's it we mean 00:16:59.839 --> 00:17:01.930 align:start position:0% Microsoft to publish that's it we mean like<00:17:00.019> under<00:17:00.440> under<00:17:00.860> the<00:17:01.010> covers<00:17:01.640> in<00:17:01.850> the 00:17:01.930 --> 00:17:01.940 align:start position:0% like under under the covers in the 00:17:01.940 --> 00:17:03.850 align:start position:0% like under under the covers in the trenches<00:17:02.329> right<00:17:02.750> to<00:17:02.870> get<00:17:03.019> you<00:17:03.260> some<00:17:03.470> products 00:17:03.850 --> 00:17:03.860 align:start position:0% trenches right to get you some products 00:17:03.860 --> 00:17:07.299 align:start position:0% trenches right to get you some products that's<00:17:04.510> not<00:17:05.510> a<00:17:05.540> lot<00:17:05.780> of<00:17:05.809> not<00:17:06.709> our<00:17:06.829> research 00:17:07.299 --> 00:17:07.309 align:start position:0% that's not a lot of not our research 00:17:07.309 --> 00:17:09.010 align:start position:0% that's not a lot of not our research everything<00:17:07.520> that<00:17:07.819> I've<00:17:08.059> mentioned<00:17:08.270> today<00:17:08.569> has 00:17:09.010 --> 00:17:09.020 align:start position:0% everything that I've mentioned today has 00:17:09.020 --> 00:17:11.890 align:start position:0% everything that I've mentioned today has been<00:17:09.199> already<00:17:09.380> published<00:17:10.299> and<00:17:11.299> the<00:17:11.449> rest<00:17:11.660> is 00:17:11.890 --> 00:17:11.900 align:start position:0% been already published and the rest is 00:17:11.900 --> 00:17:15.010 align:start position:0% been already published and the rest is well<00:17:12.110> you<00:17:12.230> know<00:17:12.459> working<00:17:13.459> hard<00:17:13.790> to<00:17:13.970> put<00:17:14.929> it 00:17:15.010 --> 00:17:15.020 align:start position:0% well you know working hard to put it 00:17:15.020 --> 00:17:15.990 align:start position:0% well you know working hard to put it externally<00:17:15.559> at<00:17:15.650> the<00:17:15.709> mall 00:17:15.990 --> 00:17:16.000 align:start position:0% externally at the mall 00:17:16.000 --> 00:17:17.549 align:start position:0% externally at the mall and<00:17:16.329> it's<00:17:16.539> great<00:17:16.689> to<00:17:16.750> hear<00:17:16.929> because<00:17:17.110> you<00:17:17.289> know 00:17:17.549 --> 00:17:17.559 align:start position:0% and it's great to hear because you know 00:17:17.559 --> 00:17:20.370 align:start position:0% and it's great to hear because you know we<00:17:17.880> in<00:17:18.880> the<00:17:19.030> community<00:17:19.419> have<00:17:19.720> for<00:17:20.230> instance 00:17:20.370 --> 00:17:20.380 align:start position:0% we in the community have for instance 00:17:20.380 --> 00:17:22.529 align:start position:0% we in the community have for instance figure-eight<00:17:20.799> for<00:17:21.039> macro<00:17:21.429> flour<00:17:21.730> which<00:17:22.209> do<00:17:22.510> a 00:17:22.529 --> 00:17:22.539 align:start position:0% figure-eight for macro flour which do a 00:17:22.539 --> 00:17:24.419 align:start position:0% figure-eight for macro flour which do a lot<00:17:22.720> of<00:17:22.750> human<00:17:23.260> yes<00:17:23.589> can<00:17:23.890> be<00:17:23.919> dangerous<00:17:24.309> I 00:17:24.419 --> 00:17:24.429 align:start position:0% lot of human yes can be dangerous I 00:17:24.429 --> 00:17:26.069 align:start position:0% lot of human yes can be dangerous I think<00:17:24.640> this<00:17:24.730> topic<00:17:25.030> is<00:17:25.150> actually<00:17:25.600> kind<00:17:26.020> of 00:17:26.069 --> 00:17:26.079 align:start position:0% think this topic is actually kind of 00:17:26.079 --> 00:17:28.020 align:start position:0% think this topic is actually kind of very<00:17:26.439> interested<00:17:27.130> into<00:17:27.370> the<00:17:27.459> motive<00:17:27.760> of 00:17:28.020 --> 00:17:28.030 align:start position:0% very interested into the motive of 00:17:28.030 --> 00:17:30.480 align:start position:0% very interested into the motive of people<00:17:28.809> in<00:17:29.289> this<00:17:29.500> community<00:17:29.650> so<00:17:29.980> this<00:17:30.280> is 00:17:30.480 --> 00:17:30.490 align:start position:0% people in this community so this is 00:17:30.490 --> 00:17:32.190 align:start position:0% people in this community so this is great<00:17:30.760> to<00:17:30.850> have<00:17:30.880> you<00:17:31.030> here<00:17:31.270> looking<00:17:31.900> for<00:17:31.929> their 00:17:32.190 --> 00:17:32.200 align:start position:0% great to have you here looking for their 00:17:32.200 --> 00:17:35.410 align:start position:0% great to have you here looking for their dog<00:17:32.409> thank<00:17:32.770> you<00:17:32.860> for<00:17:32.919> invitations 00:17:35.410 --> 00:17:35.420 align:start position:0% dog thank you for invitations 00:17:35.420 --> 00:17:38.559 align:start position:0% dog thank you for invitations [Music]