id
stringlengths 6
12
| topic_list
listlengths 2
8
| general_query_list
listlengths 1
1
| specific_query_list
listlengths 3
16
| meeting_transcripts
listlengths 91
1.83k
|
|---|---|---|---|---|
Bdb001
|
[
{
"relevant_text_span": [
[
"19",
"89"
]
],
"topic": "Current XML format to link up different components in data"
},
{
"relevant_text_span": [
[
"90",
"197"
]
],
"topic": "Best way to store features"
},
{
"relevant_text_span": [
[
"198",
"460"
]
],
"topic": "Exploring NIST's ATLAS as a potential storage format"
},
{
"relevant_text_span": [
[
"463",
"594"
]
],
"topic": "Disadvantages of ATLAS and other options"
},
{
"relevant_text_span": [
[
"595",
"760"
]
],
"topic": "Handling annotations"
}
] |
[
{
"answer": "Meeting participants wanted to agree upon a standard database to link up different components of the transcripts. The current idea was to use an XML script, but it quickly seemed that other options, like a pfile or ATLAS, are more suitable. The reason being that they would make it easier to deal with different linguistic units, like frames and utterances. Eventually, the team was skeptical of using something that would be hard to learn, like ATLAS. Nonetheless, they wanted to explore their options. The meeting finished with some discussion about handling annotations.",
"query": "Summarize the whole meeting"
}
] |
[
{
"answer": "C developed an XML format that links together utterances based on time tags, essentially creating a lattice. The XML format would be divided into many sections, each with its own ID and timeline tag. The XML format could be modified to deal with smaller linguistic units since that would only entail changing the timestamps. Despite being easy to use, the format was not efficient for smaller linguistic units, like phones. It would work for word units, at best.",
"query": "Summarize the discussion about the current XML format to link up different components in data",
"relevant_text_span": [
[
"19",
"89"
]
]
},
{
"answer": "F was concerned about how the time labels would adjust to smaller phonetic units. F inquired if the time boundaries could be changed by propagating new information throughout the XML. F thought that they could configure different XML files to deal with different units, but it would lead to large file sizes.",
"query": "What did F think about the current XML format to link up different components in data?",
"relevant_text_span": [
[
"51",
"87"
]
]
},
{
"answer": "A had seen an example of this kind of XML format before. A thought that the time boundaries were nicely handled but believed that smaller linguistic units would drain too much memory. It was essentially like a lattice, in his opinion. Though, A did not seem too concerned with dealing with smaller linguistic units since the problem would not be encountered frequently.",
"query": "What did A think about the current XML format to link up different components in data?",
"relevant_text_span": [
[
"56",
"77"
]
]
},
{
"answer": "Since the team is familiar with Perl and a flat file format is easier, it was suggested that the cost of learning a new framework, like ATLAS, might be too high. It was suggested that ATLAS be used for the external file representation initially, and if it seems suitable, then it should be adopted in its entirety. P files were also discussed but the problem with them was that they could still get pretty big.",
"query": "Summarize the discussion about the disadvantages of ATLAS and other options",
"relevant_text_span": [
[
"463",
"594"
]
]
},
{
"answer": "C thought that other options have a big learning curve, which should be taken into account, and that a flat format works well. A flat file format may not be fast, but everyone can handle it. C believed that quick and dirty solutions should be balanced with long-term infrastructural solutions. For instance, Perl can be paired with external representations of ATLAS files to create a working system. C also suggested that alternatives to P files might be interesting too, though the disadvantage would, once again, be the learning curve.",
"query": "What did C think about the disadvantages of ATLAS and other options?",
"relevant_text_span": [
[
"463",
"474"
],
[
"492",
"498"
],
[
"530",
"545"
]
]
},
{
"answer": "F wanted to ensure that prosodic features could be dealt with at the level of small linguistic units. F proposed that they be attached to the word or segment level with the option of extracting smaller units. This would allow the team to keep what they have without starting over.",
"query": "What did F think about the disadvantages of ATLAS and other options?",
"relevant_text_span": [
[
"484",
"495"
]
]
}
] |
[
{
"content": "Yeah , we had a long discussion about how much w how easy we want to make it for people to bleep things out . So {disfmarker} Morgan wants to make it hard .",
"speaker": "Grad C"
},
{
"content": "It {disfmarker} it doesn't {disfmarker}",
"speaker": "PhD D"
},
{
"content": "Did {disfmarker} did {disfmarker} did it {disfmarker} ? I didn't even check yesterday whether it was moving .",
"speaker": "Grad C"
},
{
"content": "It didn't move yesterday either when I started it .",
"speaker": "PhD D"
},
{
"content": "So .",
"speaker": "Grad C"
},
{
"content": "So I don't know if it doesn't like both of us {disfmarker}",
"speaker": "PhD D"
},
{
"content": "Channel three ? Channel three ?",
"speaker": "Grad C"
},
{
"content": "You know , I discovered something yesterday on these , um , wireless ones .",
"speaker": "PhD D"
},
{
"content": "Channel two .",
"speaker": "Grad B"
},
{
"content": "Mm - hmm ?",
"speaker": "Grad C"
},
{
"content": "You can tell if it 's picking up {pause} breath noise and stuff .",
"speaker": "PhD D"
},
{
"content": "Yeah , it has a little indicator on it {disfmarker} on the AF .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm . So if you {disfmarker} yeah , if you breathe under {disfmarker} breathe and then you see AF go off , then you know {pause} it 's p picking up your mouth noise .",
"speaker": "PhD D"
},
{
"content": "Oh , that 's good . Cuz we have a lot of breath noises .",
"speaker": "PhD F"
},
{
"content": "Yep . Test .",
"speaker": "Grad C"
},
{
"content": "In fact , if you listen to just the channels of people not talking , it 's like \" @ @ \" . It 's very disgust",
"speaker": "PhD F"
},
{
"content": "What ? Did you see Hannibal recently or something ?",
"speaker": "Grad C"
},
{
"content": "Sorry . Exactly . It 's very disconcerting . OK . So , um ,",
"speaker": "PhD F"
},
{
"content": "",
"speaker": "Grad C"
},
{
"content": "I was gonna try to get out of here , like , in half an hour , um , cuz I really appreciate people coming , and {vocalsound} the main thing that I was gonna ask people to help with today is {pause} to give input on what kinds of database format we should {pause} use in starting to link up things like word transcripts and annotations of word transcripts , so anything that transcribers or discourse coders or whatever put in the signal , {vocalsound} with time - marks for , like , words and phone boundaries and all the stuff we get out of the forced alignments and the recognizer . So , we have this , um {disfmarker} I think a starting point is clearly the {disfmarker} the channelized {pause} output of Dave Gelbart 's program , which Don brought a copy of ,",
"speaker": "PhD F"
},
{
"content": "Yeah . Yeah , I 'm {disfmarker} I 'm familiar with that . I mean , we {disfmarker} I sort of already have developed an XML format for this sort of stuff .",
"speaker": "Grad C"
},
{
"content": "um , which {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Can I see it ?",
"speaker": "PhD D"
},
{
"content": "And so the only question {disfmarker} is it the sort of thing that you want to use or not ? Have you looked at that ? I mean , I had a web page up .",
"speaker": "Grad C"
},
{
"content": "Right . So ,",
"speaker": "PhD F"
},
{
"content": "So {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I actually mostly need to be able to link up , or {disfmarker} I it 's {disfmarker} it 's a question both of what the representation is and {disfmarker}",
"speaker": "PhD F"
},
{
"content": "You mean , this {disfmarker} I guess I am gonna be standing up and drawing on the board .",
"speaker": "Grad C"
},
{
"content": "OK , yeah . So you should , definitely .",
"speaker": "PhD F"
},
{
"content": "Um , so {disfmarker} so it definitely had that as a concept . So tha it has a single time - line ,",
"speaker": "Grad C"
},
{
"content": "Mm - hmm .",
"speaker": "PhD F"
},
{
"content": "and then you can have lots of different sections , each of which have I Ds attached to it , and then you can refer from other sections to those I Ds , if you want to . So that , um {disfmarker} so that you start with {disfmarker} with a time - line tag . \" Time - line \" . And then you have a bunch of times . I don't e I don't remember exactly what my notation was ,",
"speaker": "Grad C"
},
{
"content": "Oh , I remember seeing an example of this .",
"speaker": "PhD A"
},
{
"content": "but it {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Right , right .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "Yeah , \" T equals one point three two \" , uh {disfmarker} And then I {disfmarker} I also had optional things like accuracy , and then \" ID equals T one , uh , one seven \" . And then , {nonvocalsound} I also wanted to {disfmarker} to be i to be able to not specify specifically what the time was and just have a stamp .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD F"
},
{
"content": "Yeah , so these are arbitrary , assigned by a program , not {disfmarker} not by a user . So you have a whole bunch of those . And then somewhere la further down you might have something like an utterance tag which has \" start equals T - seventeen , end equals T - eighteen \" . So what that 's saying is , we know it starts at this particular time . We don't know when it ends .",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "Right ? But it ends at this T - eighteen , which may be somewhere else . We say there 's another utterance . We don't know what the t time actually is but we know that it 's the same time as this end time .",
"speaker": "Grad C"
},
{
"content": "Mmm .",
"speaker": "PhD A"
},
{
"content": "You know , thirty - eight , whatever you want .",
"speaker": "Grad C"
},
{
"content": "So you 're essentially defining a lattice .",
"speaker": "PhD A"
},
{
"content": "OK . Yes , exactly .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "And then , uh {disfmarker} and then these also have I Ds . Right ? So you could {disfmarker} you could have some sort of other {disfmarker} other tag later in the file that would be something like , um , oh , I don't know , {comment} uh , {nonvocalsound} \" noise - type equals {nonvocalsound} door - slam \" . You know ? And then , uh , {nonvocalsound} you could either say \" time equals a particular time - mark \" or you could do other sorts of references . So {disfmarker} or {disfmarker} or you might have a prosody {disfmarker} \" Prosody \" right ? D ? T ? D ? T ? T ?",
"speaker": "Grad C"
},
{
"content": "It 's an O instead of an I , but the D is good .",
"speaker": "PhD F"
},
{
"content": "You like the D ? That 's a good D .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "Um , you know , so you could have some sort of type here , and then you could have , um {disfmarker} the utterance that it 's referring to could be U - seventeen or something like that .",
"speaker": "Grad C"
},
{
"content": "OK . So , I mean , that seems {disfmarker} that seems g great for all of the encoding of things with time and ,",
"speaker": "PhD F"
},
{
"content": "Oh , well .",
"speaker": "Grad C"
},
{
"content": "um {disfmarker} I {disfmarker} I guess my question is more , uh , what d what do you do with , say , a forced alignment ?",
"speaker": "PhD F"
},
{
"content": "How - how",
"speaker": "PhD A"
},
{
"content": "I mean you 've got all these phone labels , and what do you do if you {disfmarker} just conceptually , if you get , um , transcriptions where the words are staying but the time boundaries are changing , cuz you 've got a new recognition output , or s sort of {disfmarker} what 's the , um , sequence of going from the waveforms that stay the same , the transcripts that may or may not change , and then the utterance which {disfmarker} where the time boundaries that may or may not change {disfmarker} ?",
"speaker": "PhD F"
},
{
"content": "Oh , that 's {disfmarker} That 's actually very nicely handled here because you could {disfmarker} you could {disfmarker} all you 'd have to change is the , {vocalsound} um , time - stamps in the time - line without {disfmarker} without , uh , changing the I Ds .",
"speaker": "PhD A"
},
{
"content": "Um . And you 'd be able to propagate all of the {disfmarker} the information ?",
"speaker": "PhD F"
},
{
"content": "Right . That 's , the who that 's why you do that extra level of indirection . So that you can just change the time - line .",
"speaker": "Grad C"
},
{
"content": "Except the time - line is gonna be huge . If you say {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Yes .",
"speaker": "Grad C"
},
{
"content": "Yeah ,",
"speaker": "PhD F"
},
{
"content": "suppose you have a phone - level alignment .",
"speaker": "PhD A"
},
{
"content": "yeah , especially at the phone - level .",
"speaker": "PhD F"
},
{
"content": "You 'd have {disfmarker} you 'd have {disfmarker}",
"speaker": "PhD A"
},
{
"content": "The {disfmarker} we {disfmarker} we have phone - level backtraces .",
"speaker": "PhD F"
},
{
"content": "Yeah , this {disfmarker} I don't think I would do this for phone - level . I think for phone - level you want to use some sort of binary representation",
"speaker": "Grad C"
},
{
"content": "Um {disfmarker}",
"speaker": "PhD F"
},
{
"content": "because it 'll be too dense otherwise .",
"speaker": "Grad C"
},
{
"content": "OK . So , if you were doing that and you had this sort of companion , uh , thing that gets called up for phone - level , uh , what would that look like ?",
"speaker": "PhD F"
},
{
"content": "Why",
"speaker": "PhD A"
},
{
"content": "I would use just an existing {disfmarker} an existing way of doing it .",
"speaker": "Grad C"
},
{
"content": "How would you {disfmarker} ?",
"speaker": "PhD F"
},
{
"content": "Mmm . But {disfmarker} but why not use it for phone - level ?",
"speaker": "PhD A"
},
{
"content": "H h",
"speaker": "PhD F"
},
{
"content": "It 's just a matter of {disfmarker} it 's just a matter of it being bigger . But if you have {disfmarker} you know , barring memory limitations , or uh {disfmarker} I w I mean this is still the m",
"speaker": "PhD A"
},
{
"content": "It 's parsing limitations . I don't want to have this text file that you have to read in the whole thing to do something very simple for .",
"speaker": "Grad C"
},
{
"content": "Oh , no . You would use it only {pause} for {pause} purposes where you actually want the phone - level information , I 'd imagine .",
"speaker": "PhD A"
},
{
"content": "So you could have some file that configures how much information you want in your {disfmarker} in your XML or something .",
"speaker": "PhD F"
},
{
"content": "Right . I mean , you 'd {disfmarker} y",
"speaker": "Grad C"
},
{
"content": "Um ,",
"speaker": "PhD F"
},
{
"content": "You {disfmarker}",
"speaker": "PhD A"
},
{
"content": "I {disfmarker} I am imagining you 'd have multiple versions of this depending on the information that you want .",
"speaker": "Grad C"
},
{
"content": "cuz th it does get very bush with {disfmarker} Right .",
"speaker": "PhD F"
},
{
"content": "Um , I 'm just {disfmarker} what I 'm wondering is whether {disfmarker} I think for word - level , this would be OK .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "For word - level , it 's alright .",
"speaker": "Grad C"
},
{
"content": "Yeah . Definitely .",
"speaker": "PhD F"
},
{
"content": "Mm - hmm .",
"speaker": "PhD A"
},
{
"content": "For lower than word - level , you 're talking about so much data that I just {disfmarker} I don't know . I don't know if that {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I mean , we actually have {disfmarker} So , one thing that Don is doing , is we 're {disfmarker} we 're running {disfmarker} For every frame , you get a pitch value ,",
"speaker": "PhD F"
},
{
"content": "Lattices are big , too .",
"speaker": "PhD D"
},
{
"content": "and not only one pitch value but different kinds of pitch values",
"speaker": "PhD F"
},
{
"content": "Yeah , I mean , for something like that I would use P - file",
"speaker": "Grad C"
},
{
"content": "depending on {disfmarker}",
"speaker": "PhD F"
},
{
"content": "or {disfmarker} or any frame - level stuff I would use P - file .",
"speaker": "Grad C"
},
{
"content": "Meaning {disfmarker} ?",
"speaker": "PhD F"
},
{
"content": "Uh , that 's a {disfmarker} well , or something like it . It 's ICS uh , ICSI has a format for frame - level representation of features . Um .",
"speaker": "Grad C"
},
{
"content": "OK . That you could call {disfmarker} that you would tie into this representation with like an ID .",
"speaker": "PhD F"
},
{
"content": "Right . Right . Or {disfmarker} or there 's a {disfmarker} there 's a particular way in XML to refer to external resources .",
"speaker": "Grad C"
},
{
"content": "And {disfmarker} OK .",
"speaker": "PhD F"
},
{
"content": "So you would say \" refer to this external file \" . Um , so that external file wouldn't be in {disfmarker}",
"speaker": "Grad C"
},
{
"content": "So that might {disfmarker} that might work .",
"speaker": "PhD F"
},
{
"content": "But what {disfmarker} what 's the advantage of doing that versus just putting it into this format ?",
"speaker": "PhD D"
},
{
"content": "More compact , which I think is {disfmarker} is better .",
"speaker": "Grad C"
},
{
"content": "Uh - huh .",
"speaker": "PhD D"
},
{
"content": "I mean , if you did it at this {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I mean these are long meetings and with {disfmarker} for every frame ,",
"speaker": "PhD F"
},
{
"content": "You don't want to do it with that {disfmarker} Anything at frame - level you had better encode binary",
"speaker": "Grad C"
},
{
"content": "um {disfmarker}",
"speaker": "PhD F"
},
{
"content": "or it 's gonna be really painful .",
"speaker": "Grad C"
},
{
"content": "Or you just compre I mean , I like text formats . Um , b you can always , uh , G - zip them , and , um , you know , c decompress them on the fly if y if space is really a concern .",
"speaker": "PhD A"
},
{
"content": "Yeah , I was thi I was thinking the advantage is that we can share this with other people .",
"speaker": "PhD D"
},
{
"content": "Well , but if you 're talking about one per frame , you 're talking about gigabyte - size files . You 're gonna actually run out of space in your filesystem for one file .",
"speaker": "Grad C"
},
{
"content": "These are big files . These are really {disfmarker} I mean {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Right ? Because you have a two - gigabyte limit on most O Ss .",
"speaker": "Grad C"
},
{
"content": "Right , OK . I would say {disfmarker} OK , so frame - level is probably not a good idea . But for phone - level stuff it 's perfectly {disfmarker}",
"speaker": "PhD A"
},
{
"content": "And th it 's {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Like phones , or syllables , or anything like that .",
"speaker": "PhD A"
},
{
"content": "Phones are every five frames though , so . Or something like that .",
"speaker": "PhD F"
},
{
"content": "But {disfmarker} but {disfmarker} but most of the frames are actually not speech . So , you know , people don't {disfmarker} v Look at it , words times the average {disfmarker} The average number of phones in an English word is , I don't know , {comment} five maybe ?",
"speaker": "PhD A"
},
{
"content": "Yeah , but we actually {disfmarker}",
"speaker": "PhD F"
},
{
"content": "So , look at it , t number of words times five . That 's not {disfmarker} that not {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Oh , so you mean pause phones take up a lot of the {disfmarker} long pause phones .",
"speaker": "PhD F"
},
{
"content": "Exactly .",
"speaker": "PhD A"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "Yeah . OK . That 's true . But you do have to keep them in there . Y yeah .",
"speaker": "PhD F"
},
{
"content": "So I think it {disfmarker} it 's debatable whether you want to do phone - level in the same thing .",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "But I think , a anything at frame - level , even P - file , is too verbose .",
"speaker": "Grad C"
},
{
"content": "OK . So {disfmarker}",
"speaker": "PhD F"
},
{
"content": "I would use something tighter than P - files .",
"speaker": "Grad C"
},
{
"content": "Do you {disfmarker} Are you familiar with it ?",
"speaker": "PhD F"
},
{
"content": "So .",
"speaker": "Grad C"
},
{
"content": "I haven't seen this particular format ,",
"speaker": "PhD F"
},
{
"content": "I mean , I 've {disfmarker} I 've used them .",
"speaker": "PhD A"
},
{
"content": "but {disfmarker}",
"speaker": "PhD F"
},
{
"content": "I don't know what their structure is .",
"speaker": "PhD A"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "I 've forgot what the str",
"speaker": "PhD A"
},
{
"content": "But , wait a minute , P - file for each frame is storing a vector of cepstral or PLP values ,",
"speaker": "PhD D"
},
{
"content": "It 's whatever you want , actually .",
"speaker": "Grad C"
},
{
"content": "right ? Right .",
"speaker": "PhD D"
},
{
"content": "So that {disfmarker} what 's nice about the P - file {disfmarker} It {disfmarker} i Built into it is the concept of {pause} frames , utterances , sentences , that sort of thing , that structure . And then also attached to it is an arbitrary vector of values . And it can take different types .",
"speaker": "Grad C"
},
{
"content": "Oh .",
"speaker": "PhD F"
},
{
"content": "So it {disfmarker} th they don't all have to be floats . You know , you can have integers and you can have doubles , and all that sort of stuff .",
"speaker": "Grad C"
},
{
"content": "So that {disfmarker} that sounds {disfmarker} that sounds about what I w",
"speaker": "PhD F"
},
{
"content": "Um . Right ? And it has a header {disfmarker} it has a header format that {pause} describes it {pause} to some extent . So , the only problem with it is it 's actually storing the {pause} utterance numbers and the {pause} frame numbers in the file , even though they 're always sequential . And so it does waste a lot of space .",
"speaker": "Grad C"
},
{
"content": "Hmm .",
"speaker": "PhD A"
},
{
"content": "But it 's still a lot tighter than {disfmarker} than ASCII . And we have a lot of tools already to deal with it .",
"speaker": "Grad C"
},
{
"content": "You do ? OK . Is there some documentation on this somewhere ?",
"speaker": "PhD F"
},
{
"content": "Yeah , there 's a ton of it . Man - pages and , uh , source code , and me .",
"speaker": "Grad C"
},
{
"content": "OK , great . So , I mean , that sounds good . I {disfmarker} I was just looking for something {disfmarker} I 'm not a database person , but something sort of standard enough that , you know , if we start using this we can give it out , other people can work on it ,",
"speaker": "PhD F"
},
{
"content": "Yeah , it 's not standard .",
"speaker": "Grad C"
},
{
"content": "or {disfmarker} {comment} Is it {disfmarker} ?",
"speaker": "PhD F"
},
{
"content": "I mean , it 's something that we developed at ICSI . But , uh {disfmarker}",
"speaker": "Grad C"
},
{
"content": "But it 's {pause} been used here",
"speaker": "PhD F"
},
{
"content": "But it 's been used here",
"speaker": "Grad C"
},
{
"content": "and people 've {disfmarker}",
"speaker": "PhD F"
},
{
"content": "and {disfmarker} and , you know , we have a {pause} well - configured system that you can distribute for free , and {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I mean , it must be the equivalent of whatever you guys used to store feat your computed features in , right ?",
"speaker": "PhD D"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "Yeah , th we have {disfmarker} Actually , we {disfmarker} we use a generalization of the {disfmarker} the Sphere format .",
"speaker": "PhD A"
},
{
"content": "Mmm .",
"speaker": "PhD D"
},
{
"content": "Um , but {disfmarker} Yeah , so there is something like that but it 's , um , probably not as sophist",
"speaker": "PhD A"
},
{
"content": "Well , what does H T K do for features ?",
"speaker": "Grad C"
},
{
"content": "And I think there 's {disfmarker}",
"speaker": "PhD D"
},
{
"content": "Or does it even have a concept of features ?",
"speaker": "Grad C"
},
{
"content": "They ha it has its own {disfmarker} I mean , Entropic has their own feature format that 's called , like , S - SD or some so SF or something like that .",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "I 'm just wondering , would it be worth while to use that instead ?",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD D"
},
{
"content": "Hmm ?",
"speaker": "PhD A"
},
{
"content": "Yeah . Th - this is exactly the kind of decision {disfmarker} It 's just whatever {disfmarker}",
"speaker": "PhD F"
},
{
"content": "But , I mean , people don't typically share this kind of stuff , right ?",
"speaker": "PhD D"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "They generate their own .",
"speaker": "Grad C"
},
{
"content": "I mean {disfmarker} Yeah .",
"speaker": "PhD D"
},
{
"content": "Actually , I {disfmarker} I just {disfmarker} you know , we {disfmarker} we 've done this stuff on prosodics and three or four places have asked for those prosodic files , and we just have an ASCII , uh , output of frame - by - frame .",
"speaker": "PhD F"
},
{
"content": "Ah , right .",
"speaker": "Grad C"
},
{
"content": "Which is fine , but it gets unwieldy to go in and {disfmarker} and query these files with really huge files .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "I mean , we could do it . I was just thinking if there 's something that {disfmarker} where all the frame values are {disfmarker}",
"speaker": "PhD F"
},
{
"content": "And a and again , if you have a {disfmarker} if you have a two - hour - long meeting , that 's gonna {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Hmm ? They 're {disfmarker} they 're fair they 're quite large .",
"speaker": "PhD F"
},
{
"content": "Yeah , I mean , they 'd be emo enormous .",
"speaker": "Grad C"
},
{
"content": "And these are for ten - minute Switchboard conversations ,",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "and {disfmarker} So it 's doable , it 's just that you can only store a feature vector at frame - by - frame and it doesn't have any kind of ,",
"speaker": "PhD F"
},
{
"content": "Is {disfmarker} is the sharing part of this a pretty important {pause} consideration",
"speaker": "PhD D"
},
{
"content": "um {disfmarker}",
"speaker": "PhD F"
},
{
"content": "or does that just sort of , uh {disfmarker} a nice thing to have ?",
"speaker": "PhD D"
},
{
"content": "I {disfmarker} I don't know enough about what we 're gonna do with the data . But I thought it would be good to get something that we can {disfmarker} that other people can use or adopt for their own kinds of encoding . And just , I mean we have to use some we have to make some decision about what to do .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "And especially for the prosody work , what {disfmarker} what it ends up being is you get features from the signal , and of course those change every time your alignments change . So you re - run a recognizer , you want to recompute your features , um , and then keep the database up to date .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "Or you change a word , or you change a {vocalsound} utterance boundary segment , which is gonna happen a lot . And so I wanted something where {pause} all of this can be done in a elegant way and that if somebody wants to try something or compute something else , that it can be done flexibly . Um , it doesn't have to be pretty , it just has to be , you know , easy to use , and {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Yeah , the other thing {disfmarker} We should look at ATLAS , the NIST thing ,",
"speaker": "Grad C"
},
{
"content": "Oh .",
"speaker": "PhD F"
},
{
"content": "Mmm .",
"speaker": "PhD A"
},
{
"content": "and see if they have anything at that level .",
"speaker": "Grad C"
},
{
"content": "Uh {disfmarker}",
"speaker": "PhD F"
},
{
"content": "I mean , I 'm not sure what to do about this with ATLAS , because they chose a different route . I chose something that {disfmarker} Th - there are sort of two choices . Your {disfmarker} your file format can know about {disfmarker} know that you 're talking about language {pause} and speech , which is what I chose , and time , or your file format can just be a graph representation . And then the application has to impose the structure on top . So what it looked like ATLAS chose is , they chose the other way , which was their file format is just nodes and links , and you have to interpret what they mean yourself .",
"speaker": "Grad C"
},
{
"content": "And why did you not choose that type of approach ?",
"speaker": "PhD F"
},
{
"content": "Uh , because I knew that we were doing speech , and I thought it was better if you 're looking at a raw file to be {disfmarker} t for the tags to say \" it 's an utterance \" , as opposed to the tag to say \" it 's a link \" .",
"speaker": "Grad C"
},
{
"content": "OK . OK .",
"speaker": "PhD F"
},
{
"content": "So , but {disfmarker}",
"speaker": "Grad C"
},
{
"content": "But other than that , are they compatible ? I mean , you could sort of {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Yeah , they 're reasonably compatible .",
"speaker": "Grad C"
},
{
"content": "I mean , you {disfmarker} you could {disfmarker}",
"speaker": "PhD F"
},
{
"content": "You could probably translate between them .",
"speaker": "PhD D"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Yeah , that 's w So ,",
"speaker": "PhD F"
},
{
"content": "So , well , the other thing is if we choose to use ATLAS , which maybe we should just do , we should just throw this out before we invest a lot of time in it .",
"speaker": "Grad C"
},
{
"content": "OK . I don't {disfmarker} So this is what the meeting 's about ,",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "just sort of how to {disfmarker} Um , cuz we need to come up with a database like this just to do our work . And I actually don't care , as long as it 's something useful to other people , what we choose .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "So maybe it 's {disfmarker} maybe oth you know , if {disfmarker} if you have any idea of how to choose , cuz I don't .",
"speaker": "PhD F"
},
{
"content": "The only thing {disfmarker} Yeah .",
"speaker": "Grad C"
},
{
"content": "Do they already have tools ?",
"speaker": "PhD A"
},
{
"content": "I mean , I {disfmarker} I chose this for a couple reasons . One of them is that it 's easy to parse . You don't need a full XML parser . It 's very easy to just write a Perl script {pause} to parse it .",
"speaker": "Grad C"
},
{
"content": "As long as uh each tag is on one line .",
"speaker": "PhD A"
},
{
"content": "Exactly . Exactly . Which I always do .",
"speaker": "Grad C"
},
{
"content": "And you can have as much information in the tag as you want , right ?",
"speaker": "PhD F"
},
{
"content": "Well , I have it structured . Right ? So each type tag has only particular items that it can take .",
"speaker": "Grad C"
},
{
"content": "Can you {disfmarker} But you can add to those structures if you {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Sure . If you have more information . So what {disfmarker} What NIST would say is that instead of doing this , you would say something like \" link {nonvocalsound} start equals , um , you know , some node ID ,",
"speaker": "Grad C"
},
{
"content": "Yeah . So {disfmarker}",
"speaker": "PhD F"
},
{
"content": "end equals some other node ID \" , and then \" type \" would be \" utterance \" .",
"speaker": "Grad C"
},
{
"content": "Hmm .",
"speaker": "PhD A"
},
{
"content": "You know , so it 's very similar .",
"speaker": "Grad C"
},
{
"content": "So why would it be a {disfmarker} a waste to do it this way if it 's similar enough that we can always translate it ?",
"speaker": "PhD F"
},
{
"content": "It probably wouldn't be a waste . It would mean that at some point if we wanted to switch , we 'd just have to translate everything .",
"speaker": "PhD D"
},
{
"content": "Write a translator . But it se Since they are developing a big {disfmarker}",
"speaker": "Grad C"
},
{
"content": "But it {disfmarker} but that sounds {disfmarker}",
"speaker": "PhD F"
},
{
"content": "But that 's {disfmarker} I don't think that 's a big deal .",
"speaker": "PhD D"
},
{
"content": "As long as it is {disfmarker}",
"speaker": "PhD F"
},
{
"content": "they 're developing a big infrastructure . And so it seems to me that if {disfmarker} if we want to use that , we might as well go directly to what they 're doing , rather than {disfmarker}",
"speaker": "Grad C"
},
{
"content": "If we want to {disfmarker} Do they already have something that 's {disfmarker} that would be useful for us in place ?",
"speaker": "PhD A"
},
{
"content": "Yeah . See , that 's the question . I mean , how stable is their {disfmarker} Are they ready to go ,",
"speaker": "PhD D"
},
{
"content": "The {disfmarker} I looked at it {disfmarker}",
"speaker": "Grad C"
},
{
"content": "or {disfmarker} ?",
"speaker": "PhD D"
},
{
"content": "The last time I looked at it was a while ago , probably a year ago , uh , when we first started talking about this .",
"speaker": "Grad C"
},
{
"content": "Hmm .",
"speaker": "PhD D"
},
{
"content": "And at that time at least {vocalsound} it was still not very {pause} complete . And so , specifically they didn't have any external format representation at that time . They just had the sort of conceptual {pause} node {disfmarker} uh , annotated transcription graph , which I really liked . And that 's exactly what this stuff is based on . Since then , they 've developed their own external file format , which is , uh , you know , this sort of s this sort of thing . Um , and apparently they 've also developed a lot of tools , but I haven't looked at them . Maybe I should .",
"speaker": "Grad C"
},
{
"content": "We should {disfmarker} we should find out .",
"speaker": "PhD A"
},
{
"content": "I mean , would the tools {disfmarker} would the tools run on something like this , if you can translate them anyway ?",
"speaker": "PhD F"
},
{
"content": "Um , th what would {disfmarker} would {disfmarker} would {disfmarker} what would worry me is that maybe we might miss a little detail",
"speaker": "Grad C"
},
{
"content": "It 's a hassle",
"speaker": "PhD A"
},
{
"content": "I mean , that {disfmarker} I guess it 's a question that {disfmarker}",
"speaker": "PhD F"
},
{
"content": "if {disfmarker}",
"speaker": "PhD A"
},
{
"content": "uh , yeah .",
"speaker": "PhD F"
},
{
"content": "that would make it very difficult to translate from one to the other .",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "I {disfmarker} I think if it 's conceptually close , and they already have or will have tools that everybody else will be using , I mean , {vocalsound} it would be crazy to do something s you know , separate that {disfmarker}",
"speaker": "PhD A"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "Yeah , we might as well . Yep .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "So I 'll {disfmarker} I 'll take a closer look at it .",
"speaker": "Grad C"
},
{
"content": "Actually , so it 's {disfmarker} that {disfmarker} that would really be the question , is just what you would feel is in the long run the best thing .",
"speaker": "PhD F"
},
{
"content": "And {disfmarker} Right .",
"speaker": "Grad C"
},
{
"content": "Cuz {vocalsound} once we start , sort of , doing this I don't {disfmarker} we don't actually have enough time to probably have to rehash it out again",
"speaker": "PhD F"
},
{
"content": "The {disfmarker} Yep . The other thing {disfmarker} the other way that I sort of established this was as easy translation to and from the Transcriber format .",
"speaker": "Grad C"
},
{
"content": "and {disfmarker} s Right .",
"speaker": "PhD F"
},
{
"content": "Um ,",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD F"
},
{
"content": "but {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I mean , I like this . This is sort of intuitively easy to actually r read ,",
"speaker": "PhD F"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "as easy it could {disfmarker} as it could be . But , I suppose that {pause} as long as they have a type here that specifies \" utt \" , um ,",
"speaker": "PhD F"
},
{
"content": "It 's almost the same .",
"speaker": "Grad C"
},
{
"content": "it 's {disfmarker} yeah , close enough that {disfmarker}",
"speaker": "PhD F"
},
{
"content": "The {disfmarker} the {disfmarker} the {disfmarker} the point is {disfmarker} with this , though , is that you can't really add any supplementary information . Right ? So if you suddenly decide that you want {disfmarker}",
"speaker": "Grad C"
},
{
"content": "You have to make a different type .",
"speaker": "PhD F"
},
{
"content": "Yeah . You 'd have to make a different type .",
"speaker": "Grad C"
},
{
"content": "So {disfmarker} Well , if you look at it and {disfmarker} Um , I guess in my mind I don't know enough {disfmarker} Jane would know better , {comment} about the {pause} types of annotations and {disfmarker} and {disfmarker} But I imagine that those are things that would {disfmarker} well , you guys mentioned this , {comment} that could span any {disfmarker} it could be in its own channel , it could span time boundaries of any type ,",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "it could be instantaneous , things like that . Um , and then from the recognition side we have backtraces at the phone - level .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "If {disfmarker} if it can handle that , it could handle states or whatever . And then at the prosody - level we have frame {disfmarker} sort of like cepstral feature files ,",
"speaker": "PhD F"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "uh , like these P - files or anything like that . And that 's sort of the world of things that I {disfmarker} And then we have the aligned channels , of course ,",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "It seems to me you want to keep the frame - level stuff separate .",
"speaker": "PhD A"
},
{
"content": "and {disfmarker} Yeah .",
"speaker": "PhD F"
},
{
"content": "And then {disfmarker}",
"speaker": "PhD A"
},
{
"content": "I {disfmarker} I definitely agree and I wanted to find actually a f a nicer format or a {disfmarker} maybe a more compact format than what we used before .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "Just cuz you 've got {vocalsound} ten channels or whatever and two hours of a meeting . It 's {disfmarker} it 's a lot of {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Huge .",
"speaker": "Grad C"
},
{
"content": "Now {disfmarker} now how would you {disfmarker} how would you represent , um , multiple speakers in this framework ? Were {disfmarker} You would just represent them as {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Um ,",
"speaker": "Grad C"
},
{
"content": "You would have like a speaker tag or something ?",
"speaker": "PhD A"
},
{
"content": "there 's a spea speaker tag up at the top which identifies them and then each utt the way I had it is each turn or each utterance , {comment} I don't even remember now , had a speaker ID tag attached to it .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm . OK .",
"speaker": "PhD A"
},
{
"content": "And in this format you would have a different tag , which {disfmarker} which would , uh , be linked to the link . So {disfmarker} so somewhere else you would have another thing {pause} that would be ,",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "um {disfmarker} Let 's see , would it be a node or a link ? Um {disfmarker} And so {disfmarker} so this one would have , um , an ID is link {disfmarker} {comment} link seventy - four or something like that .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm .",
"speaker": "PhD A"
},
{
"content": "And then somewhere up here you would have a link that {disfmarker} that , uh , you know , was referencing L - seventy - four and had speaker Adam .",
"speaker": "Grad C"
},
{
"content": "Is i ?",
"speaker": "PhD A"
},
{
"content": "You know , or something like that .",
"speaker": "Grad C"
},
{
"content": "Actually , it 's the channel , I think , that {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Well , channel or speaker or whatever .",
"speaker": "PhD A"
},
{
"content": "I mean , w yeah , channel is what the channelized output out",
"speaker": "PhD F"
},
{
"content": "It doesn't {disfmarker}",
"speaker": "PhD A"
},
{
"content": "This isn't quite right .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "I have to look at it again .",
"speaker": "Grad C"
},
{
"content": "Yeah , but {disfmarker}",
"speaker": "PhD F"
},
{
"content": "But {disfmarker} but {disfmarker} so how in the NIST format do we express {vocalsound} a hierarchical relationship between , um , say , an utterance and the words within it ? So how do you {pause} tell {pause} that {pause} these are the words that belong to that utterance ?",
"speaker": "PhD A"
},
{
"content": "Um , you would have another structure lower down than this that would be saying they 're all belonging to this ID .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm .",
"speaker": "PhD A"
},
{
"content": "So each thing refers to the {pause} utterance that it belongs to .",
"speaker": "PhD D"
},
{
"content": "Right . And then each utterance could refer to a turn ,",
"speaker": "Grad C"
},
{
"content": "So it 's {disfmarker} it 's not hi it 's sort of bottom - up .",
"speaker": "PhD D"
},
{
"content": "and each turn could refer to something higher up .",
"speaker": "Grad C"
},
{
"content": "And what if you actually have {disfmarker} So right now what you have as utterance , um , the closest thing that comes out of the channelized is the stuff between the segment boundaries that the transcribers put in or that Thilo put in , which may or may not actually be , like , a s it 's usually not {disfmarker} um , the beginning and end of a sentence , say .",
"speaker": "PhD F"
},
{
"content": "Well , that 's why I didn't call it \" sentence \" .",
"speaker": "Grad C"
},
{
"content": "So , right . Um , so it 's like a segment or something .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "So , I mean , I assume this is possible , that if you have {disfmarker} someone annotates the punctuation or whatever when they transcribe , you can say , you know , from {disfmarker} for {disfmarker} from the c beginning of the sentence to the end of the sentence , from the annotations , this is a unit , even though it never actually {disfmarker} i It 's only a unit by virtue of the annotations {pause} at the word - level .",
"speaker": "PhD F"
},
{
"content": "Sure . I mean , so you would {disfmarker} you would have yet another tag .",
"speaker": "Grad C"
},
{
"content": "And then that would get a tag somehow .",
"speaker": "PhD F"
},
{
"content": "You 'd have another tag which says this is of type \" sentence \" .",
"speaker": "Grad C"
},
{
"content": "OK . OK .",
"speaker": "PhD F"
},
{
"content": "And , what {disfmarker}",
"speaker": "Grad C"
},
{
"content": "But it 's just not overtly in the {disfmarker}",
"speaker": "PhD F"
},
{
"content": "OK .",
"speaker": "PhD A"
},
{
"content": "Um , cuz this is exactly the kind of {disfmarker}",
"speaker": "PhD F"
},
{
"content": "So {disfmarker}",
"speaker": "PhD A"
},
{
"content": "I think that should be {pause} possible as long as the {disfmarker} But , uh , what I don't understand is where the {disfmarker} where in this type of file {pause} that would be expressed .",
"speaker": "PhD F"
},
{
"content": "Right . You would have another tag somewhere . It 's {disfmarker} well , there 're two ways of doing it .",
"speaker": "Grad C"
},
{
"content": "S so it would just be floating before the sentence or floating after the sentence without a time - mark .",
"speaker": "PhD F"
},
{
"content": "You could have some sort of link type {disfmarker} type equals \" sentence \" , and ID is \" S - whatever \" . And then lower down you could have an utterance . So the type is \" utterance \" {disfmarker} equals \" utt \" . And you could either say that {disfmarker} No . I don't know {disfmarker}",
"speaker": "Grad C"
},
{
"content": "So here 's the thing .",
"speaker": "PhD A"
},
{
"content": "I take that back .",
"speaker": "Grad C"
},
{
"content": "Um {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Can you {disfmarker} can you say that this is part of this ,",
"speaker": "Grad C"
},
{
"content": "See , cuz it 's {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Hhh .",
"speaker": "PhD A"
},
{
"content": "it 's {disfmarker}",
"speaker": "PhD F"
},
{
"content": "You would just have a r",
"speaker": "PhD D"
},
{
"content": "S",
"speaker": "PhD F"
},
{
"content": "or do you say this is part of this ? I think {disfmarker}",
"speaker": "Grad C"
},
{
"content": "You would refer up to the sentence .",
"speaker": "PhD D"
},
{
"content": "But they 're {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Well , the thing {disfmarker}",
"speaker": "PhD A"
},
{
"content": "they 're actually overlapping each other , sort of .",
"speaker": "PhD F"
},
{
"content": "So {disfmarker}",
"speaker": "Grad C"
},
{
"content": "the thing is that some something may be a part of one thing for one purpose and another thing of another purpose .",
"speaker": "PhD A"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "So f",
"speaker": "PhD A"
},
{
"content": "You have to have another type then , I guess .",
"speaker": "PhD F"
},
{
"content": "s Um , well , s let 's {disfmarker} let 's ta so let 's {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Well , I think I 'm {disfmarker} I think w I had better look at it again",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "so {disfmarker}",
"speaker": "PhD A"
},
{
"content": "because I {disfmarker} I 'm {disfmarker}",
"speaker": "Grad C"
},
{
"content": "OK . OK .",
"speaker": "PhD F"
},
{
"content": "y So for instance @ @ {comment} sup",
"speaker": "PhD A"
},
{
"content": "There 's one level {disfmarker} there 's one more level of indirection that I 'm forgetting .",
"speaker": "Grad C"
},
{
"content": "Suppose you have a word sequence and you have two different segmentations of that same word sequence . f Say , one segmentation is in terms of , um , you know , uh , sentences . And another segmentation is in terms of , um , {vocalsound} I don't know , {comment} prosodic phrases . And let 's say that they don't {pause} nest . So , you know , a prosodic phrase may cross two sentences or something .",
"speaker": "PhD A"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "I don't know if that 's true or not but {vocalsound} let 's as",
"speaker": "PhD A"
},
{
"content": "Well , it 's definitely true with the segment .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "That 's what I {disfmarker} exactly what I meant by the utterances versus the sentence could be sort of {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Yeah . So , you want to be s you want to say this {disfmarker} this word is part of that sentence and this prosodic phrase .",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "But the phrase is not part of the sentence",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "and neither is the sentence part of the phrase .",
"speaker": "PhD A"
},
{
"content": "Right .",
"speaker": "PhD F"
},
{
"content": "I I 'm pretty sure that you can do that , but I 'm forgetting the exact level of nesting .",
"speaker": "Grad C"
},
{
"content": "So , you would have to have {vocalsound} two different pointers from the word up {disfmarker} one level up , one to the sent",
"speaker": "PhD A"
},
{
"content": "So {disfmarker} so what you would end up having is a tag saying \" here 's a word , and it starts here and it ends here \" .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "And then lower down you would say \" here 's a prosodic boundary and it has these words in it \" . And lower down you 'd have \" here 's a sentence ,",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "An - Right .",
"speaker": "PhD F"
},
{
"content": "and it has these words in it \" .",
"speaker": "Grad C"
},
{
"content": "So you would be able to go in and say , you know , \" give me all the words in the bound in the prosodic phrase",
"speaker": "PhD F"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "and give me all the words in the {disfmarker} \" Yeah .",
"speaker": "PhD F"
},
{
"content": "So I think that 's {disfmarker} that would wor",
"speaker": "Grad C"
},
{
"content": "Um , OK .",
"speaker": "PhD F"
},
{
"content": "Let me look at it again .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm . The {disfmarker} the o the other issue that you had was , how do you actually efficiently extract , um {disfmarker} find and extract information in a structure of this type ?",
"speaker": "PhD A"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "So .",
"speaker": "Grad C"
},
{
"content": "That 's good .",
"speaker": "PhD F"
},
{
"content": "So you gave some examples like {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Well , uh , and , I mean , you guys might {disfmarker} I don't know if this is premature because I suppose once you get the representation you can do this , but the kinds of things I was worried about is ,",
"speaker": "PhD F"
},
{
"content": "No , that 's not clear .",
"speaker": "PhD A"
},
{
"content": "uh {disfmarker}",
"speaker": "PhD F"
},
{
"content": "I mean , yeah , you c sure you can do it ,",
"speaker": "PhD A"
},
{
"content": "Well , OK . So i if it {disfmarker}",
"speaker": "PhD F"
},
{
"content": "but can you do it sort of l l you know , it {disfmarker}",
"speaker": "PhD A"
},
{
"content": "I I mean , I can't do it , but I can {disfmarker} um ,",
"speaker": "PhD F"
},
{
"content": "y y you gotta {disfmarker} you gotta do this {disfmarker} you {disfmarker} you 're gonna want to do this very quickly",
"speaker": "PhD A"
},
{
"content": "Well {disfmarker}",
"speaker": "Grad C"
},
{
"content": "or else you 'll spend all your time sort of searching through very {vocalsound} complex data structures {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Right . You 'd need a p sort of a paradigm for how to do it . But an example would be \" find all the cases in which Adam started to talk while Andreas was talking and his pitch was rising , Andreas 's pitch \" . That kind of thing .",
"speaker": "PhD F"
},
{
"content": "Right . I mean , that 's gonna be {disfmarker} Is the rising pitch a {pause} feature , or is it gonna be in the same file ?",
"speaker": "Grad C"
},
{
"content": "Well , the rising pitch will never be {pause} hand - annotated . So the {disfmarker} all the prosodic features are going to be automatically {disfmarker}",
"speaker": "PhD F"
},
{
"content": "But the {disfmarker} I mean , that 's gonna be hard regardless ,",
"speaker": "Grad C"
},
{
"content": "So they 're gonna be in those {disfmarker}",
"speaker": "PhD F"
},
{
"content": "right ? Because you 're gonna have to write a program that goes through your feature file and looks for rising pitches .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "So {disfmarker} Right . So normally what we would do is we would say \" what do we wanna assign rising pitch to ? \" Are we gonna assign it to words ? Are we gonna just assign it to sort of {disfmarker} when it 's rising we have a begin - end rise representation ? But suppose we dump out this file and we say , uh , for every word we just classify it as , w you know , rise or fall or neither ?",
"speaker": "PhD F"
},
{
"content": "OK . Well , in that case you would add that to this {pause} format",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "r",
"speaker": "Grad C"
},
{
"content": "So we would basically be sort of , um , taking the format and enriching it with things that we wanna query in relation to the words that are already in the file ,",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "and then querying it .",
"speaker": "PhD F"
},
{
"content": "You want sort of a grep that 's {disfmarker} that works at the structural {disfmarker} on the structural representation .",
"speaker": "PhD A"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "You have that . There 's a {pause} standard again in XML , specifically for searching XML documents {disfmarker} structured X - XML documents , where you can specify both the content and the structural position .",
"speaker": "Grad C"
},
{
"content": "Yeah , but it 's {disfmarker} it 's not clear that that 's {disfmarker} That 's relative to the structure of the XML document ,",
"speaker": "PhD A"
},
{
"content": "If {disfmarker}",
"speaker": "PhD F"
},
{
"content": "not to the structure of what you 're representing in the document .",
"speaker": "PhD A"
},
{
"content": "You use it as a tool . You use it as a tool , not an end - user . It 's not an end - user thing .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "It 's {disfmarker} it 's {disfmarker} you would use that to build your tool to do that sort of search .",
"speaker": "Grad C"
},
{
"content": "Right . Be Because here you 're specifying a lattice .",
"speaker": "PhD A"
},
{
"content": "Uh {disfmarker}",
"speaker": "PhD F"
},
{
"content": "So the underlying {disfmarker} that 's the underlying data structure . And you want to be able to search in that lattice .",
"speaker": "PhD A"
},
{
"content": "But as long as the {disfmarker}",
"speaker": "PhD F"
},
{
"content": "It 's a graph , but {disfmarker}",
"speaker": "Grad C"
},
{
"content": "That 's different from searching through the text .",
"speaker": "PhD A"
},
{
"content": "But it seems like as long as the features that {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Well , no , no , no . The whole point is that the text and the lattice are isomorphic . They {pause} represent each other {pause} completely .",
"speaker": "Grad C"
},
{
"content": "Um {disfmarker}",
"speaker": "PhD A"
},
{
"content": "So that {disfmarker} I mean th",
"speaker": "Grad C"
},
{
"content": "That 's true if the features from your acoustics or whatever that are not explicitly in this are at the level of these types .",
"speaker": "PhD F"
},
{
"content": "Hhh .",
"speaker": "PhD A"
},
{
"content": "That {disfmarker} that if you can do that {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Yeah , but that 's gonna be the trouble no matter what . Right ? No matter what format you choose , you 're gonna have the trou you 're gonna have the difficulty of relating the {disfmarker} the frame - level features {disfmarker}",
"speaker": "Grad C"
},
{
"content": "That 's right . That 's true . That 's why I was trying to figure out what 's the best format for this representation .",
"speaker": "PhD F"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "And it 's still gonna be {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Hmm .",
"speaker": "PhD A"
},
{
"content": "it 's still gonna be , uh , not direct .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "You know , it {disfmarker} Or another example was , you know , uh , where in the language {disfmarker} where in the word sequence are people interrupting ? So , I guess that one 's actually easier .",
"speaker": "PhD F"
},
{
"content": "What about {disfmarker} what about , um , the idea of using a relational database to , uh , store the information from the XML ? So you would have {disfmarker} XML basically would {disfmarker} Uh , you {disfmarker} you could use the XML to put the data in , and then when you get data out , you put it back in XML . So use XML as sort of the {disfmarker} the transfer format ,",
"speaker": "PhD D"
},
{
"content": "Transfer .",
"speaker": "Grad C"
},
{
"content": "uh , but then you store the data in the database , which allows you to do all kinds of {pause} good search things in there .",
"speaker": "PhD D"
},
{
"content": "The , uh {disfmarker} One of the things that ATLAS is doing is they 're trying to define an API which is independent of the back store ,",
"speaker": "Grad C"
},
{
"content": "Huh .",
"speaker": "PhD F"
},
{
"content": "so that , uh , you could define a single API and the {disfmarker} the storage could be flat XML files or a database .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm .",
"speaker": "PhD D"
},
{
"content": "My opinion on that is for the s sort of stuff that we 're doing , {comment} I suspect it 's overkill to do a full relational database , that , um , just a flat file and , uh , search tools I bet will be enough .",
"speaker": "Grad C"
},
{
"content": "But {disfmarker}",
"speaker": "PhD A"
},
{
"content": "But that 's the advantage of ATLAS , is that if we actually take {disfmarker} decide to go that route completely and we program to their API , then if we wanted to add a database later it would be pretty easy .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm . Mm - hmm .",
"speaker": "PhD D"
},
{
"content": "It seems like the kind of thing you 'd do if {disfmarker} I don't know , if people start adding all kinds of s bells and whistles to the data . And so that might be {disfmarker} I mean , it 'd be good for us to know {disfmarker} to use a format where we know we can easily , um , input that to some database if other people are using it .",
"speaker": "PhD F"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Something like that .",
"speaker": "PhD F"
},
{
"content": "I guess I 'm just a little hesitant to try to go whole hog on sort of the {disfmarker} the whole framework that {disfmarker} that NIST is talking about , with ATLAS and a database and all that sort of stuff ,",
"speaker": "Grad C"
},
{
"content": "So {disfmarker}",
"speaker": "PhD F"
},
{
"content": "cuz it 's a big learning curve , just to get going .",
"speaker": "Grad C"
},
{
"content": "Hmm .",
"speaker": "PhD D"
},
{
"content": "Hmm .",
"speaker": "PhD A"
},
{
"content": "Whereas if we just do a flat file format , sure , it may not be as efficient but everyone can program in Perl and {disfmarker} and use it .",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "Right ?",
"speaker": "Grad C"
},
{
"content": "But this is {disfmarker}",
"speaker": "PhD A"
},
{
"content": "So , as opposed to {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I {disfmarker} I 'm still , um , {vocalsound} not convinced that you can do much at all on the text {disfmarker} on the flat file that {disfmarker} that {disfmarker} you know , the text representation . e Because the text representation is gonna be , uh , not reflecting the structure of {disfmarker} of your words and annotations . It 's just {disfmarker} it 's {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Well , if it 's not representing it , then how do you recover it ? Of course it 's representing it .",
"speaker": "Grad C"
},
{
"content": "No . You {disfmarker} you have to {disfmarker} what you have to do is you have to basically {disfmarker}",
"speaker": "PhD A"
},
{
"content": "That 's the whole point .",
"speaker": "Grad C"
},
{
"content": "Y yeah . You can use Perl to read it in and construct a internal representation that is essentially a lattice . But , the {disfmarker} and then {disfmarker}",
"speaker": "PhD A"
},
{
"content": "OK .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD D"
},
{
"content": "Well , that was a different point .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "Right ? So what I was saying is that {disfmarker}",
"speaker": "Grad C"
},
{
"content": "But that 's what you 'll have to do . Bec - be",
"speaker": "PhD A"
},
{
"content": "For Perl {disfmarker} if you want to just do Perl . If you wanted to use the structured XML query language , that 's a different thing . And it 's a set of tools {vocalsound} that let you specify given the D - DDT {disfmarker} DTD of the document , um , what sorts of structural searches you want to do . So you want to say that , you know , you 're looking for , um , a tag within a tag within a particular tag that has this particular text in it , um , and , uh , refers to a particular value . And so the point isn't that an end - user , who is looking for a query like you specified , wouldn't program it in this language . What you would do is , someone would build a tool that used that as a library . So that they {disfmarker} so that you wouldn't have to construct the internal representations yourself .",
"speaker": "Grad C"
},
{
"content": "Is a {disfmarker} See , I think the kinds of questions , at least in the next {disfmarker} to the end of this year , are {disfmarker} there may be a lot of different ones , but they 'll all have a similar nature . They 'll be looking at either a word - level prosodic , uh , an {disfmarker} a value ,",
"speaker": "PhD F"
},
{
"content": "Mm - hmm .",
"speaker": "Grad C"
},
{
"content": "like a continuous value , like the slope of something . But you know , we 'll do something where we {disfmarker} some kind of data reduction where the prosodic features are sort o uh , either at the word - level or at the segment - level ,",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "or {disfmarker} or something like that . They 're not gonna be at the phone - level and they 're no not gonna be at the frame - level when we get done with sort of giving them simpler shapes and things . And so the main thing is just being able {disfmarker} Well , I guess , the two goals . Um , one that Chuck mentioned is starting out with something that we don't have to start over , that we don't have to throw away if other people want to extend it for other kinds of questions ,",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "and being able to at least get enough , uh , information out on {disfmarker} where we condition the location of features on information that 's in the kind of file that you {pause} put up there . And that would {disfmarker} that would do it ,",
"speaker": "PhD F"
},
{
"content": "Yeah . I think that there are quick and dirty solutions ,",
"speaker": "Grad C"
},
{
"content": "I mean , for me .",
"speaker": "PhD F"
},
{
"content": "and then there are long - term , big - infrastructure solutions . And so {vocalsound} we want to try to pick something that lets us do a little bit of both .",
"speaker": "Grad C"
},
{
"content": "In the between , right . And especially that the representation doesn't have to be thrown away ,",
"speaker": "PhD F"
},
{
"content": "Um {disfmarker} Right .",
"speaker": "Grad C"
},
{
"content": "even if your tools change .",
"speaker": "PhD F"
},
{
"content": "And so it seems to me that {disfmarker} I mean , I have to look at it again to see whether it can really do what we want , but if we use the ATLAS external file representation , um , it seems like it 's rich enough that you could do quick tools just as I said in Perl , and then later on if we choose to go up the learning curve , we can use the whole ATLAS inter infrastructure ,",
"speaker": "Grad C"
},
{
"content": "Yeah . I mean , that sounds good to me .",
"speaker": "PhD F"
},
{
"content": "which has all that built in .",
"speaker": "Grad C"
},
{
"content": "I {disfmarker} I don't {disfmarker} So if {disfmarker} if you would l look at that and let us know what you think .",
"speaker": "PhD F"
},
{
"content": "Sure .",
"speaker": "Grad C"
},
{
"content": "I mean , I think we 're sort of guinea pigs , cuz I {disfmarker} I want to get the prosody work done but I don't want to waste time , you know , getting the {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Oh , maybe {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Yeah ?",
"speaker": "PhD F"
},
{
"content": "um {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Well , I wouldn't wait for the formats , because anything you pick we 'll be able to translate to another form .",
"speaker": "Grad C"
},
{
"content": "Well {disfmarker} Ma well , maybe you should actually look at it yourself too to get a sense of what it is you 'll {disfmarker} you 'll be dealing with ,",
"speaker": "PhD A"
},
{
"content": "OK .",
"speaker": "PhD F"
},
{
"content": "because , um , you know , Adam might have one opinion but you might have another , so",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "Grad B"
},
{
"content": "Yeah , definitely .",
"speaker": "PhD F"
},
{
"content": "I think the more eyes look at this the better .",
"speaker": "PhD A"
},
{
"content": "Especially if there 's , e um {disfmarker} you know , if someone can help with at least the {disfmarker} the setup of the right {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Hi , Jane .",
"speaker": "Grad C"
},
{
"content": "Oh , hi .",
"speaker": "PhD F"
},
{
"content": "Mmm .",
"speaker": "PhD A"
},
{
"content": "the right representation , then , i you know , I hope it won't {disfmarker} We don't actually need the whole full - blown thing to be ready ,",
"speaker": "PhD F"
},
{
"content": "Can you {disfmarker} Oh , well .",
"speaker": "Grad C"
},
{
"content": "so . Um , so maybe if you guys can look at it and sort of see what ,",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Grad B"
},
{
"content": "Sure .",
"speaker": "Grad C"
},
{
"content": "um {disfmarker} I think we 're {disfmarker} we 're {disfmarker} {vocalsound} we 're actually just {disfmarker}",
"speaker": "PhD F"
},
{
"content": "We 're about done .",
"speaker": "Grad C"
},
{
"content": "yeah ,",
"speaker": "PhD F"
},
{
"content": "Hmm .",
"speaker": "Grad B"
},
{
"content": "wrapping up , but , um {disfmarker} Yeah , sorry , it 's a uh short meeting , but , um {disfmarker} Well , I don't know . Is there anything else , like {disfmarker} I mean that helps me a lot ,",
"speaker": "PhD F"
},
{
"content": "Well , I think the other thing we might want to look at is alternatives to P - file .",
"speaker": "Grad C"
},
{
"content": "but {disfmarker}",
"speaker": "PhD F"
},
{
"content": "I mean , th the reason I like P - file is I 'm already familiar with it , we have expertise here , and so if we pick something else , there 's the learning - curve problem . But , I mean , it is just something we developed at ICSI .",
"speaker": "Grad C"
},
{
"content": "Is there an {disfmarker} is there an IP - API ?",
"speaker": "PhD A"
},
{
"content": "And so {disfmarker} Yeah .",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD A"
},
{
"content": "There 's an API for it . And , uh ,",
"speaker": "Grad C"
},
{
"content": "There used to be a problem that they get too large ,",
"speaker": "PhD A"
},
{
"content": "a bunch of libraries , P - file utilities .",
"speaker": "Grad C"
},
{
"content": "and so {pause} basically the {disfmarker} uh the filesystem wouldn't {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Well , that 's gonna be a problem no matter what . You have the two - gigabyte limit on the filesystem size . And we definitely hit that with Broadcast News .",
"speaker": "Grad C"
},
{
"content": "Maybe you could extend the API to , uh , support , uh , like splitting up , you know , conceptually one file into smaller files on disk so that you can essentially , you know , have arbitrarily long f",
"speaker": "PhD A"
},
{
"content": "Yep . Most of the tools can handle that .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "So that we didn't do it at the API - level . We did it at the t tool - level . That {disfmarker} that {disfmarker} most {disfmarker} many of them can s you can specify several P - files and they 'll just be done sequentially .",
"speaker": "Grad C"
},
{
"content": "OK .",
"speaker": "PhD A"
},
{
"content": "So .",
"speaker": "Grad C"
},
{
"content": "So , I guess , yeah , if {disfmarker} if you and Don can {disfmarker} if you can show him the P - file stuff and see .",
"speaker": "PhD F"
},
{
"content": "Sure .",
"speaker": "Grad C"
},
{
"content": "So this would be like for the F - zero {disfmarker}",
"speaker": "PhD F"
},
{
"content": "True .",
"speaker": "Grad B"
},
{
"content": "I mean , if you do \" man P - file \" or \" apropos P - file \" , you 'll see a lot .",
"speaker": "Grad C"
},
{
"content": "I 've used the P - file , I think . I 've looked at it at least , briefly , I think when we were doing s something .",
"speaker": "Grad B"
},
{
"content": "What does the P stand for anyway ?",
"speaker": "PhD A"
},
{
"content": "I have no idea .",
"speaker": "Grad C"
},
{
"content": "Oh , in there .",
"speaker": "Grad B"
},
{
"content": "I didn't de I didn't develop it . You know , it was {disfmarker} I think it was Dave Johnson . So it 's all part of the Quicknet library . It has all the utilities for it .",
"speaker": "Grad C"
},
{
"content": "No , P - files were around way before Quicknet . P - files were {disfmarker} were around when {disfmarker} w with , um , {vocalsound} RAP .",
"speaker": "PhD A"
},
{
"content": "Oh , were they ?",
"speaker": "Grad C"
},
{
"content": "Mm - hmm .",
"speaker": "PhD D"
},
{
"content": "Right ?",
"speaker": "PhD A"
},
{
"content": "It 's like the history of ICSI .",
"speaker": "PhD F"
},
{
"content": "You worked with P - files .",
"speaker": "PhD A"
},
{
"content": "Mm - hmm .",
"speaker": "Grad C"
},
{
"content": "Like {disfmarker}",
"speaker": "PhD F"
},
{
"content": "No .",
"speaker": "PhD D"
},
{
"content": "I worked with P - files .",
"speaker": "PhD A"
},
{
"content": "Yeah ?",
"speaker": "PhD F"
},
{
"content": "I don't remember what the \" P \" is , though .",
"speaker": "PhD D"
},
{
"content": "No .",
"speaker": "PhD A"
},
{
"content": "But there are ni they 're {disfmarker} The {pause} Quicknet library has a bunch of things in it to handle P - files ,",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "so it works pretty well .",
"speaker": "Grad C"
},
{
"content": "",
"speaker": "PhD A"
},
{
"content": "And that isn't really , I guess , as important as the {disfmarker} the main {disfmarker} I don't know what you call it , the {disfmarker} the main sort of word - level {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Neither do I .",
"speaker": "Grad C"
},
{
"content": "Probably stands for \" Phil \" . Phil Kohn .",
"speaker": "PhD D"
},
{
"content": "It 's a Phil file ?",
"speaker": "Grad C"
},
{
"content": "Yeah . That 's my guess .",
"speaker": "PhD D"
},
{
"content": "Huh . OK . Well , that 's really useful . I mean , this is exactly the kind of thing that I wanted to settle . Um , so {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Yeah , I 've been meaning to look at the ATLAS stuff again anyway .",
"speaker": "Grad C"
},
{
"content": "Great .",
"speaker": "PhD F"
},
{
"content": "So , just keep {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Yeah . I guess it 's also sort of a political deci I mean , if {disfmarker} if you feel like that 's a community that would be good to tie into anyway , then it 's {disfmarker} sounds like it 's worth doing .",
"speaker": "PhD F"
},
{
"content": "Yeah , I think it {disfmarker} it w",
"speaker": "Grad C"
},
{
"content": "j I think there 's {disfmarker}",
"speaker": "PhD A"
},
{
"content": "And , w uh , as I said , I {disfmarker} what I did with this stuff {disfmarker} I based it on theirs . It 's just they hadn't actually come up with an external format yet . So now that they have come up with a format , it doesn't {disfmarker} it seems pretty reasonable to use it .",
"speaker": "Grad C"
},
{
"content": "Mmm .",
"speaker": "PhD A"
},
{
"content": "But let me look at it again .",
"speaker": "Grad C"
},
{
"content": "OK , great .",
"speaker": "PhD F"
},
{
"content": "As I said , that {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Cuz we actually can start {disfmarker}",
"speaker": "PhD F"
},
{
"content": "There 's one level {disfmarker} there 's one more level of indirection and I 'm just blanking on exactly how it works . I gotta look at it again .",
"speaker": "Grad C"
},
{
"content": "I mean , we can start with , um , I guess , this input from Dave 's , which you had printed out , the channelized input . Cuz he has all of the channels , you know , with the channels in the tag and stuff like that .",
"speaker": "PhD F"
},
{
"content": "Yeah , I 've seen it .",
"speaker": "Grad C"
},
{
"content": "So that would be i directly ,",
"speaker": "PhD F"
},
{
"content": "Yep . Easy {disfmarker} easy to map .",
"speaker": "Grad C"
},
{
"content": "um {disfmarker} Yeah . And so then it would just be a matter of getting {disfmarker} making sure to handle the annotations that are , you know , not at the word - level and , um , t to import the",
"speaker": "PhD F"
},
{
"content": "Where are those annotations coming from ?",
"speaker": "Grad B"
},
{
"content": "Well , right now , I g Jane would {disfmarker} {vocalsound} would {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Mm - hmm .",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "Are you talking about the overlap a annotations ?",
"speaker": "Postdoc E"
},
{
"content": "Yeah , any kind of annotation {pause} that , like , isn't already there . Uh , you know , anything you can envision .",
"speaker": "PhD F"
},
{
"content": "Yeah . So what I was imagining was {disfmarker} um , so Dave says we can have unlimited numbers of green ribbons . And so put , uh , a {disfmarker} a green ribbon on for an overlap code . And since we w we {disfmarker} I {disfmarker} I think it 's important to remain flexible regarding the time bins for now . And so it 's nice to have {disfmarker} However , you know , you want to have it , uh , time time uh , located in the discourse . So , um , if we {disfmarker} if we tie the overlap code to the first word in the overlap , then you 'll have a time - marking . It won't {disfmarker} it 'll be independent of the time bins , however these e evolve , shrink , or whatever , increase , or {disfmarker} Also , you could have different time bins for different purposes . And having it tied to the first word in an overlap segment is unique , uh , you know , anchored , clear . And it would just end up on a separate ribbon .",
"speaker": "Postdoc E"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "So the overlap coding is gonna be easy with respect to that . You look puzzled .",
"speaker": "Postdoc E"
},
{
"content": "I {disfmarker} I just {disfmarker} I don't quite understand what these things are .",
"speaker": "PhD D"
},
{
"content": "OK .",
"speaker": "Postdoc E"
},
{
"content": "Uh .",
"speaker": "PhD D"
},
{
"content": "What , the codes themselves ?",
"speaker": "Postdoc E"
},
{
"content": "Well , th overlap codes .",
"speaker": "PhD D"
},
{
"content": "Or the {disfmarker} ?",
"speaker": "Postdoc E"
},
{
"content": "I 'm not sure what that @ @ {disfmarker}",
"speaker": "PhD D"
},
{
"content": "Well , I mean , is that {disfmarker}",
"speaker": "Grad C"
},
{
"content": "It probably doesn't matter .",
"speaker": "PhD D"
},
{
"content": "Well , we don't have to go into the codes .",
"speaker": "Postdoc E"
},
{
"content": "I mean , it doesn't .",
"speaker": "Grad C"
},
{
"content": "No , I d",
"speaker": "PhD D"
},
{
"content": "We don't have to go into the codes .",
"speaker": "Postdoc E"
},
{
"content": "I mean , that {disfmarker} not for the topic of this meeting .",
"speaker": "Grad C"
},
{
"content": "But let me just {disfmarker} No . W the idea is just to have a separate green ribbon , you know , and {disfmarker} and {disfmarker} and let 's say that this is a time bin . There 's a word here . This is the first word of an overlapping segment of any length , overlapping with any other , uh , word {disfmarker} uh , i segment of any length . And , um , then you can indicate that this here was perhaps a ch a backchannel , or you can say that it was , um , a usurping of the turn , or you can {disfmarker} you know , any {disfmarker} any number of categories . But the fact is , you have it time - tagged in a way that 's independent of the , uh , sp particular time bin that the word ends up in . If it 's a large unit or a small unit , or",
"speaker": "Postdoc E"
},
{
"content": "Mm - hmm .",
"speaker": "PhD A"
},
{
"content": "we sh change the boundaries of the units , it 's still unique and {disfmarker} and , uh , fits with the format ,",
"speaker": "Postdoc E"
},
{
"content": "Right .",
"speaker": "PhD F"
},
{
"content": "flexible , all that .",
"speaker": "Postdoc E"
},
{
"content": "Um , it would be nice {disfmarker} um , eh , gr this is sort of r regarding {disfmarker} uh , uh it 's related but not directly germane to the topic of discussion , but , when it comes to annotations , um , you often find yourself in the situation where you have {pause} different annotations {pause} of the same , say , word sequence . OK ?",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "Postdoc E"
},
{
"content": "And sometimes the word sequences even differ slightly because they were edited s at one place but not the other .",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "Postdoc E"
},
{
"content": "So , once this data gets out there , some people might start annotating this for , I don't know , dialogue acts or , um , you know , topics or what the heck . You know , there 's a zillion things that people might annotate this for . And the only thing that is really sort of common among all the versi the various versions of this data is the word sequence , or approximately .",
"speaker": "PhD A"
},
{
"content": "Yep .",
"speaker": "Postdoc E"
},
{
"content": "Or the time .",
"speaker": "PhD F"
},
{
"content": "Or the times . But , see , if you 'd annotate dialogue acts , you don't necessarily want to {disfmarker} or topics {disfmarker} you don't really want to be dealing with time - marks .",
"speaker": "PhD A"
},
{
"content": "I guess .",
"speaker": "PhD F"
},
{
"content": "You 'd {disfmarker} it 's much more efficient for them to just see the word sequence , right ?",
"speaker": "PhD A"
},
{
"content": "Mm - hmm .",
"speaker": "PhD F"
},
{
"content": "I mean , most people aren't as sophisticated as {disfmarker} as we are here with , you know , uh , time alignments and stuff . So {disfmarker} So the {disfmarker} the {disfmarker} the point is {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Should {disfmarker} should we mention some names on the people who are n ?",
"speaker": "Grad C"
},
{
"content": "Right . So , um , the p my point is that {pause} you 're gonna end up with , uh , word sequences that are differently annotated . And {pause} you want some tool , uh , that is able to sort of merge these different annotations back into a single , uh , version . OK ? Um , and we had this problem very massively , uh , at SRI when we worked , uh , a while back on , {vocalsound} uh {disfmarker} well , on dialogue acts as well as , uh , you know , um , what was it ? uh ,",
"speaker": "PhD A"
},
{
"content": "Well , all the Switchboard in it .",
"speaker": "PhD F"
},
{
"content": "utterance types . There 's , uh , automatic , uh , punctuation and stuff like that .",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "Because we had one set of {pause} annotations that were based on , uh , one version of the transcripts with a particular segmentation , and then we had another version that was based on , uh , a different s slightly edited version of the transcripts with a different segmentation . So , {vocalsound} we had these two different versions which were {disfmarker} you know , you could tell they were from the same source but they weren't identical . So it was extremely hard {vocalsound} to reliably merge these two back together to correlate the information from the different annotations .",
"speaker": "PhD A"
},
{
"content": "Yep . I {disfmarker} I don't see any way that file formats are gonna help us with that .",
"speaker": "Grad C"
},
{
"content": "No .",
"speaker": "PhD A"
},
{
"content": "It 's {disfmarker} it 's all a question of semantic .",
"speaker": "Grad C"
},
{
"content": "No . But once you have a file format , I can imagine writing {disfmarker} not personally , but someone writing a tool that is essentially an alignment tool , um , that mediates between various versions ,",
"speaker": "PhD A"
},
{
"content": "Mm - hmm .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "and {disfmarker} uh , sort of like th uh , you know , you have this thing in UNIX where you have , uh , diff .",
"speaker": "PhD A"
},
{
"content": "Diff .",
"speaker": "Grad C"
},
{
"content": "W - diff or diff .",
"speaker": "PhD F"
},
{
"content": "There 's the , uh , diff that actually tries to reconcile different {disfmarker} two diffs f {comment} based on the same original .",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "Is it S - diff ?",
"speaker": "Postdoc E"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Mmm .",
"speaker": "Postdoc E"
},
{
"content": "Something like that , um , but operating on these lattices that are really what 's behind this {disfmarker} uh , this annotation format .",
"speaker": "PhD A"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "So {disfmarker}",
"speaker": "PhD A"
},
{
"content": "There 's actually a diff library you can use {pause} to do things like that that {disfmarker} so you have different formats .",
"speaker": "Grad C"
},
{
"content": "You could definitely do that with the {disfmarker}",
"speaker": "PhD F"
},
{
"content": "So somewhere in the API you would like to have like a merge or some {disfmarker} some function that merges two {disfmarker} two versions .",
"speaker": "PhD A"
},
{
"content": "Yeah , I think it 's gonna be very hard . Any sort of structured anything when you try to merge is really , really hard",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "because you ha i The hard part isn't the file format . The hard part is specifying what you mean by \" merge \" .",
"speaker": "Grad C"
},
{
"content": "Is {disfmarker} Exactly .",
"speaker": "PhD A"
},
{
"content": "And that 's very difficult .",
"speaker": "Grad C"
},
{
"content": "But the one thing that would work here actually for i that is more reliable than the utterances is the {disfmarker} the speaker ons and offs . So if you have a good ,",
"speaker": "PhD F"
},
{
"content": "But this is exactly what I mean , is that {disfmarker} that the problem i",
"speaker": "Grad C"
},
{
"content": "um {disfmarker} Yeah . You just have to know wha what to tie it to .",
"speaker": "PhD F"
},
{
"content": "Yeah , exactly . The problem is saying \" what are the semantics ,",
"speaker": "Grad C"
},
{
"content": "And {disfmarker}",
"speaker": "PhD F"
},
{
"content": "what do you mean by \" merge \" ? \"",
"speaker": "Grad C"
},
{
"content": "Right , right .",
"speaker": "PhD F"
},
{
"content": "Right . So {disfmarker} so just to let you know what we {disfmarker} where we kluged it by , uh , doing {disfmarker} uh , by doing {disfmarker} Hhh .",
"speaker": "PhD A"
},
{
"content": "So .",
"speaker": "Grad C"
},
{
"content": "Both were based on words , so , bo we have two versions of the same words intersp you know , sprinkled with {disfmarker} with different tags for annotations .",
"speaker": "PhD A"
},
{
"content": "And then you did diff .",
"speaker": "Grad C"
},
{
"content": "And we did diff . Exactly !",
"speaker": "PhD A"
},
{
"content": "Yeah , that 's just what I thought .",
"speaker": "Grad C"
},
{
"content": "And that 's how {disfmarker}",
"speaker": "PhD A"
},
{
"content": "That 's just wh how I would have done it .",
"speaker": "Grad C"
},
{
"content": "Yeah . But , you know , it had lots of errors and things would end up in the wrong order , and so forth . Uh , so , um , if you had a more {disfmarker}",
"speaker": "PhD A"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Uh , it {disfmarker} it was a kluge because it was basically reducing everything to {disfmarker} uh , to {disfmarker} uh , uh , to textual alignment .",
"speaker": "PhD A"
},
{
"content": "A textual {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Um , so {disfmarker}",
"speaker": "PhD A"
},
{
"content": "But , d isn't that something where whoever {disfmarker} if {vocalsound} {disfmarker} if the people who are making changes , say in the transcripts , cuz this all happened when the transcripts were different {disfmarker} ye um , if they tie it to something , like if they tied it to the acoustic segment {disfmarker} if they {disfmarker} You know what I mean ? Then {disfmarker} Or if they tied it to an acoustic segment and we had the time - marks , that would help .",
"speaker": "PhD F"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "But the problem is exactly as Adam said , that you get , you know , y you don't have that information or it 's lost in the merge somehow ,",
"speaker": "PhD F"
},
{
"content": "Well , can I ask one question ?",
"speaker": "Postdoc E"
},
{
"content": "so {disfmarker}",
"speaker": "PhD F"
},
{
"content": "It {disfmarker} it seems to me that , um , we will have o an official version of the corpus , which will be only one {disfmarker} one version in terms of the words {disfmarker} where the words are concerned . We 'd still have the {disfmarker} the merging issue maybe if coding were done independently of the {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "And you 're gonna get that",
"speaker": "PhD A"
},
{
"content": "But {disfmarker} but {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "because if the data gets out , people will do all kinds of things to it . And , uh , s you know , several years from now you might want to look into , um , the prosody of referring expressions . And someone at the university of who knows where has annotated the referring expressions . So you want to get that annotation and bring it back in line with your data .",
"speaker": "PhD A"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "OK ?",
"speaker": "PhD A"
},
{
"content": "But unfortunately they 've also hand - edited it .",
"speaker": "Grad C"
},
{
"content": "OK , then {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "But they 've also {disfmarker} Exactly . And so that 's exactly what we should {disfmarker} somehow when you distribute the data , say that {disfmarker} you know , that {disfmarker} have some way of knowing how to merge it back in and asking people to try to do that .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "PhD A"
},
{
"content": "Well , then the {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "What 's {disfmarker} what 's wrong with {pause} doing times ? I {disfmarker}",
"speaker": "PhD D"
},
{
"content": "I agree . That was what I was wondering .",
"speaker": "Postdoc E"
},
{
"content": "Uh , yeah , time is the {disfmarker}",
"speaker": "PhD F"
},
{
"content": "Well ,",
"speaker": "Grad C"
},
{
"content": "Time is unique . You were saying that you didn't think we should {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "Time is passing !",
"speaker": "PhD F"
},
{
"content": "Time {disfmarker} time {disfmarker} times are ephemeral .",
"speaker": "PhD A"
},
{
"content": "Andreas was saying {disfmarker} Yeah .",
"speaker": "Postdoc E"
},
{
"content": "what if they haven't notated with them , times ?",
"speaker": "Grad C"
},
{
"content": "Yeah . He {disfmarker} he 's a language modeling person , though .",
"speaker": "PhD F"
},
{
"content": "Um {disfmarker}",
"speaker": "PhD A"
},
{
"content": "So {disfmarker} so imagine {disfmarker} I think his {disfmarker} his example is a good one . Imagine that this person who developed the corpus of the referring expressions didn't include time .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm . Yeah .",
"speaker": "PhD A"
},
{
"content": "He included references to words .",
"speaker": "Grad C"
},
{
"content": "Ach !",
"speaker": "Postdoc E"
},
{
"content": "Yeah .",
"speaker": "PhD A"
},
{
"content": "He said that at this word is when {disfmarker} when it happened .",
"speaker": "Grad C"
},
{
"content": "Well , then {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "Or she .",
"speaker": "PhD A"
},
{
"content": "Or she .",
"speaker": "Grad C"
},
{
"content": "But then couldn't you just indirectly figure out the time {pause} tied to the word ?",
"speaker": "Postdoc E"
},
{
"content": "But still they {disfmarker} Exactly .",
"speaker": "PhD F"
},
{
"content": "Sure . But what if {disfmarker} what if they change the words ?",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "Not {disfmarker} Well , but you 'd have some anchoring point . He couldn't have changed all the words .",
"speaker": "Postdoc E"
},
{
"content": "But can they change the words without changing the time of the word ?",
"speaker": "PhD D"
},
{
"content": "Sure . But they could have changed it a little . The {disfmarker} the point is , that {disfmarker} that they may have annotated it off a word transcript that isn't the same as our word transcript , so how do you merge it back in ? I understand what you 're saying .",
"speaker": "Grad C"
},
{
"content": "Mmm . Mm - hmm .",
"speaker": "PhD A"
},
{
"content": "And I {disfmarker} I guess the answer is , um , it 's gonna be different every time . It 's j it 's just gonna be {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Yeah .",
"speaker": "Postdoc E"
},
{
"content": "Yeah .",
"speaker": "PhD F"
},
{
"content": "I it 's exactly what I said before ,",
"speaker": "Grad C"
},
{
"content": "You only know the boundaries of the {disfmarker}",
"speaker": "PhD F"
},
{
"content": "which is that \" what do you mean by \" merge \" ? \" So in this case where you have the words and you don't have the times , well , what do you mean by \" merge \" ? If you tell me what you mean , I can write a program to do it .",
"speaker": "Grad C"
},
{
"content": "Right . Right . You can merge at the level of the representation that the other person preserved and that 's it .",
"speaker": "PhD F"
},
{
"content": "Right . And that 's about all you can do .",
"speaker": "Grad C"
},
{
"content": "And beyond that , all you know is {disfmarker} is relative ordering and sometimes even that is wrong .",
"speaker": "PhD F"
},
{
"content": "So {disfmarker} so in {disfmarker} so in this one you would have to do a best match between the word sequences ,",
"speaker": "Grad C"
},
{
"content": "So .",
"speaker": "PhD F"
},
{
"content": "Mm - hmm .",
"speaker": "PhD A"
},
{
"content": "extract the times f from the best match of theirs to yours , and use that .",
"speaker": "Grad C"
},
{
"content": "And then infer that their time - marks are somewhere in between .",
"speaker": "PhD F"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "Yeah , exactly .",
"speaker": "PhD F"
},
{
"content": "But it could be that they just {disfmarker} uh , I mean , it could be that they chunked {disfmarker} they {disfmarker} they lost certain utterances and all that stuff ,",
"speaker": "Postdoc E"
},
{
"content": "Right , exactly . So it could get very , very ugly .",
"speaker": "Grad C"
},
{
"content": "or {disfmarker}",
"speaker": "Postdoc E"
},
{
"content": "Definitely .",
"speaker": "PhD F"
},
{
"content": "Yeah .",
"speaker": "Postdoc E"
},
{
"content": "Definitely . Alright .",
"speaker": "PhD F"
},
{
"content": "That 's interesting .",
"speaker": "Postdoc E"
},
{
"content": "Well , I guess , w I {disfmarker} I didn't want to keep people too long and Adam wanted t people {disfmarker} I 'll read the digits . If anyone else offers to , that 'd be great . And",
"speaker": "PhD F"
},
{
"content": "Ah , well .",
"speaker": "PhD A"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "if not , I guess {disfmarker}",
"speaker": "PhD F"
},
{
"content": "For th for the {disfmarker} {nonvocalsound} for the benefit of science we 'll read the digits .",
"speaker": "PhD A"
},
{
"content": "More digits , the better . OK , this is",
"speaker": "Grad C"
},
{
"content": "Thanks {disfmarker} thanks a lot . It 's really helpful . I mean , Adam and Don {nonvocalsound} will sort of meet and I think that 's great . Very useful . Go next .",
"speaker": "PhD F"
},
{
"content": "Scratch that .",
"speaker": "PhD D"
},
{
"content": "O three",
"speaker": "Postdoc E"
},
{
"content": "Oh , right .",
"speaker": "Grad C"
}
] |
Bed004
|
[
{
"relevant_text_span": [
[
"39",
"127"
]
],
"topic": "Details about setting up the wizard and recruiting participants"
},
{
"relevant_text_span": [
[
"140",
"186"
]
],
"topic": "Trajector - landmark and source - path - goal modifications to the Bayes net"
},
{
"relevant_text_span": [
[
"187",
"256"
]
],
"topic": "Controlling size of combinatorial input"
},
{
"relevant_text_span": [
[
"261",
"349"
]
],
"topic": "Generalizing schema to extract properties for different Bayes nets"
}
] |
[
{
"answer": "The team began the meeting by discussing the logistics of setting up the interface for data collection. Some members ran a trial of it earlier and found someone who would make a suitable wizard. The team shared concern about how they would recruit non-university student participants. Grad D introduced the team to the second iteration of the bayes-net model and its schemas. Then, the discussion moved onto controlling the size of the bayes-net as it would otherwise be based on too much information. The team ended the meeting by delving into how the method of creating a Bayes-net in different scenarios could itself be abstracted, i.e. narrowing the input and output factors and the intermediate representation.",
"query": "Summarize the meeting"
}
] |
[
{
"answer": "The team listened to a recording of the interface's trial run. Litonya was asked to be the first subject of the interface and Fey acted as the wizard. The team was happy with Fey's performance and decided to hire her. Upon Fey's suggestion, they also decided that the wizard should be introduced in a more appropriate fashion. The team also agreed that the run was too long at 5 minutes.",
"query": "Summarize the details about setting up the wizard and recruiting participants",
"relevant_text_span": [
[
"39",
"127"
]
]
},
{
"answer": "Grad C was concerned that the same person acting as the wizard and computer system might not be the best idea. Grad D had some way of making the wizard and computer seem distinct even though both were voiced by the same person and told Grad C that the recording would clarify things.",
"query": "What did Grad D and Grad C discuss about who was acting as the computer and wizard?",
"relevant_text_span": [
[
"44",
"51"
]
]
},
{
"answer": "The Professor was very supportive of the idea of hiring Fey. He thought that it would be helpful since she was also willing to take over the task of organizing subjects. In addition, he believed the project would provide her with a valuable learning experience for her own upcoming graduate school work in experimental paradigms.",
"query": "What did the Professor think about hiring Fey?",
"relevant_text_span": [
[
"95",
"115"
]
]
},
{
"answer": "The team was concerned that the combinatorial input that would result from the various linguistic and contextual schemas would be enormous for the Bayes net. The Professor suggested that it's best to narrow down the decision variables, perhaps by studying the trade-offs between different input factors. The team thought that perhaps they could keep the kinds of objects in the environment to a small subset and make rules governing actions around those objects.",
"query": "Summarize the discussion about controlling size of combinatorial input",
"relevant_text_span": [
[
"187",
"256"
]
]
},
{
"answer": "The professor was the one to raise the issue and suggested that a knowledge engineering trick could be used to narrow down inputs. He thought that perhaps adding deterministic rules to properties that have actions would be helpful and the property types could be retrieved from the ontology.",
"query": "What did the Professor think about controlling the size of the combinatorial input?",
"relevant_text_span": [
[
"187",
"201"
],
[
"227",
"239"
]
]
},
{
"answer": "Grad D thought that the best way would be to add restrictive action types that are attached to the kind of object. For instance, there are specific actions that would be relevant to a landmark.",
"query": "What did Grad D think about managing the size of the combinatorial input?",
"relevant_text_span": [
[
"220",
"224"
]
]
}
] |
[
{
"content": "Hey , you 're not supposed to be drinking in here dude .",
"speaker": "Grad A"
},
{
"content": "OK .",
"speaker": "Grad D"
},
{
"content": "Do we have to read them that slowly ? OK . Sounded like a robot . Um , this is t",
"speaker": "Grad A"
},
{
"content": "OK .",
"speaker": "Grad C"
},
{
"content": "When you read the numbers it kind of reminded me of beat poetry .",
"speaker": "Grad A"
},
{
"content": "I tried to go for the EE Cummings sort of feeling , but {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Three three six zero zero . Four two zero zero one seven . That 's what I think of when I think of beat poetry .",
"speaker": "Grad A"
},
{
"content": "Beat poetry .",
"speaker": "Grad C"
},
{
"content": "You ever seen \" So I married an axe murderer \" ?",
"speaker": "Grad A"
},
{
"content": "Uh parts of it .",
"speaker": "Grad C"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "There 's a part wh there 's parts when he 's doing beat poetry .",
"speaker": "Grad A"
},
{
"content": "Oh yeah ?",
"speaker": "Grad C"
},
{
"content": "And he talks like that . That 's why I thi That uh probably is why I think of it that way .",
"speaker": "Grad A"
},
{
"content": "Hmm . No , I didn't see that movie . Who did {disfmarker} who made that ?",
"speaker": "Grad D"
},
{
"content": "Mike Meyers is the guy .",
"speaker": "Grad A"
},
{
"content": "Oh . OK .",
"speaker": "Grad D"
},
{
"content": "It - it 's his uh {disfmarker} it 's his cute romantic comedy . That 's {disfmarker} that 's {disfmarker} That 's his cute romantic comedy , yeah . The other thing that 's real funny , I 'll spoil it for you . is when he 's {disfmarker} he works in a coffee shop , in San Francisco , and uh he 's sitting there on this couch and they bring him this massive cup of espresso , and he 's like \" excuse me I ordered the large espresso ? \"",
"speaker": "Grad A"
},
{
"content": "Uh . We 're having , {vocalsound} a tiramisu tasting contest this weekend .",
"speaker": "Grad D"
},
{
"content": "Wait {disfmarker} do are y So you 're trying to decide who 's the best taster of tiramisu ?",
"speaker": "Grad A"
},
{
"content": "No ? Um . There was a {disfmarker} a {disfmarker} a fierce argument that broke out over whose tiramisu might be the best and so we decided to have a contest where those people who claim to make good tiramisu make them ,",
"speaker": "Grad D"
},
{
"content": "Ah .",
"speaker": "Grad A"
},
{
"content": "and then we got a panel of impartial judges that will taste {disfmarker} do a blind taste {vocalsound} and then vote .",
"speaker": "Grad D"
},
{
"content": "Hmm .",
"speaker": "Grad A"
},
{
"content": "Should be fun .",
"speaker": "Grad D"
},
{
"content": "Seems like {disfmarker} Seems like you could put a s magic special ingredient in , so that everyone know which one was yours . Then , if you were to bribe them , you could uh {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Mm - hmm . Well , I was thinking if um {disfmarker} y you guys have plans for Sunday ? We 're {disfmarker} we 're not {disfmarker} it 's probably going to be this Sunday , but um we 're sort of working with the weather here because we also want to combine it with some barbecue activity where we just fire it up and what {disfmarker} whoever brings whatever you know , can throw it on there . So only the tiramisu is free , nothing else .",
"speaker": "Grad D"
},
{
"content": "Well , I 'm going back to visit my parents this weekend , so , I 'll be out of town .",
"speaker": "Grad A"
},
{
"content": "So you 're going to the west Bay then ? No ,",
"speaker": "Grad D"
},
{
"content": "No , the South Bay ,",
"speaker": "Grad A"
},
{
"content": "south Bay ?",
"speaker": "Grad D"
},
{
"content": "yeah .",
"speaker": "Grad A"
},
{
"content": "South Bay .",
"speaker": "Grad D"
},
{
"content": "Well , I should be free , so .",
"speaker": "Grad C"
},
{
"content": "OK , I 'll let you know .",
"speaker": "Grad D"
},
{
"content": "OK .",
"speaker": "Grad C"
},
{
"content": "We are . Is Nancy s uh gonna show up ? Mmm . Wonder if these things ever emit a very , like , piercing screech right in your ear ?",
"speaker": "Grad A"
},
{
"content": "They are gonna get more comfortable headsets . They already ordered them . OK .",
"speaker": "Grad D"
},
{
"content": "Uh {disfmarker}",
"speaker": "Grad C"
},
{
"content": "Let 's get started . The uh {disfmarker} Should I go first , with the uh , um , data . Can I have the remote {vocalsound} control . Thank you . OK . So . On Friday we had our wizard test data test and um {vocalsound} these are some of the results . This was the introduction . I actually uh , even though Liz was uh kind enough to offer to be the first subject , I sort of felt that she knew too much , so I asked uh Litonya . just on the spur of the moment , and she was uh kind enough to uh serve as the first subject .",
"speaker": "Grad D"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "So , this is what she saw as part of {disfmarker} as uh for instr introduction , this is what she had to read {pause} aloud . Uh , that was really difficult for her and uh {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Because of l all the names , you mean ?",
"speaker": "Grad C"
},
{
"content": "The names and um this was the uh first three tasks she had to {disfmarker} to master after she called the system , and um then of course the system broke down , and those were the l uh uh I should say the system was supposed to break down and then um these were the remaining three tasks that she was going to solve , with a human {disfmarker} Um . There are {disfmarker} here are uh the results . Mmm . And I will not {disfmarker} We will skip the reading now . D Um . And um . The reading was five minutes , exactly . And now comes the {disfmarker} This is the phone - in phase of {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Wait , can I {disfmarker} I have a question . So . So there 's no system , right ? Like , there was a wizard for both uh {disfmarker} both parts , is this right ?",
"speaker": "Grad C"
},
{
"content": "Yeah . It was bo it both times the same person .",
"speaker": "Grad D"
},
{
"content": "OK .",
"speaker": "Grad C"
},
{
"content": "One time , pretending to be a system , one time , to {disfmarker} pretending to be a human , which is actually not pretending .",
"speaker": "Grad D"
},
{
"content": "OK . And she didn't {disfmarker}",
"speaker": "Grad C"
},
{
"content": "I should {disfmarker}",
"speaker": "Grad D"
},
{
"content": "I mean . Well . Isn't this kind of obvious when it says \" OK now you 're talking to a human \" and then the human has the same voice ?",
"speaker": "Grad C"
},
{
"content": "No no no . We u Wait . OK , good question , but uh you {disfmarker} you just wait and see .",
"speaker": "Grad D"
},
{
"content": "OK .",
"speaker": "Grad C"
},
{
"content": "It 's {disfmarker} You 're gonna l learn . And um the wizard sometimes will not be audible , Because she was actually {disfmarker} they {disfmarker} there was some uh lapse in the um wireless , we have to move her closer .",
"speaker": "Grad D"
},
{
"content": "Is she mispronouncing \" Anlage \" ? Is it \" Anlaga \" or \" Anlunga \"",
"speaker": "Grad A"
},
{
"content": "They 're mispronouncing everything ,",
"speaker": "Grad D"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "but it 's {disfmarker} This is the system breaking down , actually . \" Did I call Europe ? \" So , this is it . Well , if we {disfmarker} we um",
"speaker": "Grad D"
},
{
"content": "So , are {disfmarker} are you trying to record this meeting ?",
"speaker": "Professor B"
},
{
"content": "There was a strange reflex . I have a headache . I 'm really sort of out of it . OK , the uh lessons learned . The reading needs to be shorter . Five minutes is just too long . Um , that was already anticipated by some people suggested that if we just have bullets here , they 're gonna not {disfmarker} they 're {disfmarker} subjects are probably not gonna {disfmarker} going to follow the order . And uh she did not .",
"speaker": "Grad D"
},
{
"content": "Really ?",
"speaker": "Grad C"
},
{
"content": "She {disfmarker} No .",
"speaker": "Grad D"
},
{
"content": "Oh , it 's surprising .",
"speaker": "Grad C"
},
{
"content": "She {disfmarker} she jumped around quite a bit .",
"speaker": "Grad D"
},
{
"content": "S so if you just number them \" one \" , \" two \" , \" three \" it 's",
"speaker": "Professor B"
},
{
"content": "Yeah , and make it sort of clear in the uh {disfmarker}",
"speaker": "Grad D"
},
{
"content": "OK . Right .",
"speaker": "Professor B"
},
{
"content": "Um . We need to {disfmarker} So that 's one thing . And we need a better introduction for the wizard . That is something that Fey actually thought of a {disfmarker} in the last second that sh the system should introduce itself , when it 's called .",
"speaker": "Grad D"
},
{
"content": "Mm - hmm . True .",
"speaker": "Professor B"
},
{
"content": "And um , um , another suggestion , by Liz , was that we uh , through subjects , switch the tasks . So when {disfmarker} when they have task - one with the computer , the next person should have task - one with a human , and so forth .",
"speaker": "Grad D"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "So we get nice um data for that . Um , we have to refine the tasks more and more , which of course we haven't done at all , so far , in order to avoid this rephrasing , so where , even though w we don't tell the person \" ask {pause} blah - blah - blah - blah - blah \" they still try , or at least Litonya tried to um repeat as much of that text as possible .",
"speaker": "Grad D"
},
{
"content": "Say exactly what 's on there ? Yeah .",
"speaker": "Grad C"
},
{
"content": "And uh my suggestion is of course we {disfmarker} we keep the wizard , because I think she did a wonderful job ,",
"speaker": "Grad D"
},
{
"content": "Great .",
"speaker": "Professor B"
},
{
"content": "in the sense that she responded quite nicely to things that were not asked for , \" How much is a t a bus ticket and a transfer \" so this is gonna happen all the time , we d you can never be sure .",
"speaker": "Grad D"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "Um . Johno pointed out that uh we have maybe a grammatical gender problem there with wizard .",
"speaker": "Grad D"
},
{
"content": "Yes .",
"speaker": "Grad A"
},
{
"content": "So um .",
"speaker": "Grad D"
},
{
"content": "I wasn't {disfmarker} wasn't sure whether wizard was the correct term for {pause} uh \" not a man \" .",
"speaker": "Grad A"
},
{
"content": "There 's no female equivalent of {disfmarker}",
"speaker": "Grad C"
},
{
"content": "But uh {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Are you sure ?",
"speaker": "Grad A"
},
{
"content": "No , I don't know .",
"speaker": "Grad C"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "Not that I know of .",
"speaker": "Grad C"
},
{
"content": "Well , there is witch and warlock ,",
"speaker": "Grad D"
},
{
"content": "Yeah , that 's so @ @ .",
"speaker": "Grad A"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "Yeah , that 's what I was thinking , but {disfmarker}",
"speaker": "Grad C"
},
{
"content": "and uh {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Right . Uh .",
"speaker": "Professor B"
},
{
"content": "OK . And um {disfmarker} So , some {disfmarker} some work needs to be done , but I think we can uh {disfmarker} And this , and {disfmarker} in case no {disfmarker} you hadn't seen it , this is what Litonya looked at during the uh {disfmarker} um while taking the {disfmarker} while partaking in the data collection .",
"speaker": "Grad D"
},
{
"content": "Ah .",
"speaker": "Grad C"
},
{
"content": "OK , great . So {pause} first of all , I agree that um we should hire Fey , and start paying her . Probably pay for the time she 's put in as well . Um , do you know exactly how to do that , or is uh Lila {disfmarker} I mean , you know what exactly do we do to {disfmarker} to put her on the payroll in some way ?",
"speaker": "Professor B"
},
{
"content": "I 'm completely clueless , but I 'm willing to learn .",
"speaker": "Grad D"
},
{
"content": "OK . Well , you 'll have to . Right . So anyway , um",
"speaker": "Professor B"
},
{
"content": "N",
"speaker": "Grad D"
},
{
"content": "So why don't you uh ask Lila and see what she says about you know exactly what we do for someone in th",
"speaker": "Professor B"
},
{
"content": "Student - type worker ,",
"speaker": "Grad D"
},
{
"content": "Well , yeah she 's un she 's not a {disfmarker} a student ,",
"speaker": "Professor B"
},
{
"content": "or {disfmarker} ?",
"speaker": "Grad D"
},
{
"content": "she just graduated but anyway .",
"speaker": "Professor B"
},
{
"content": "Hmm .",
"speaker": "Grad D"
},
{
"content": "So i if {disfmarker} Yeah , I agree , she sounded fine , she a actually was {pause} uh , more uh , present and stuff than {disfmarker} than she was in conversation , so she did a better job than I would have guessed from just talking to her .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad D"
},
{
"content": "So I think that 's great .",
"speaker": "Professor B"
},
{
"content": "This is sort of what I gave her , so this is for example h how to get to the student prison ,",
"speaker": "Grad D"
},
{
"content": "Yeah .",
"speaker": "Professor B"
},
{
"content": "and I didn't even spell it out here and in some cases I {disfmarker} I spelled it out a little bit um more thoroughly ,",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "this is the information on {disfmarker} on the low sunken castle , and the amphitheater that never came up , and um , so i if we give her even more um , instruments to work with I think the results are gonna be even better .",
"speaker": "Grad D"
},
{
"content": "Oh , yeah , and then of course as she does it she 'll {disfmarker} she 'll learn @ @ . So that 's great . Um {pause} And also if she 's willing to take on the job of organizing all those subjects and stuff that would be wonderful .",
"speaker": "Professor B"
},
{
"content": "Mmm .",
"speaker": "Grad D"
},
{
"content": "And , uh she 's {disfmarker} actually she 's going to graduate school in a kind of an experimental paradigm , so I think this is all just fine in terms of h her learning things she 's gonna need to know uh , to do her career .",
"speaker": "Professor B"
},
{
"content": "Mmm .",
"speaker": "Grad D"
},
{
"content": "So , I {disfmarker} my guess is she 'll be r r quite happy to take on that job . And , so {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Yep . Yeah she {disfmarker} she didn't explicitly state that so .",
"speaker": "Grad D"
},
{
"content": "Great .",
"speaker": "Professor B"
},
{
"content": "And um I told her that we gonna um figure out a meeting time in the near future to refine the tasks and s look for the potential sources to find people . She also agrees that you know if it 's all just gonna be students the data is gonna be less valuable because of that so .",
"speaker": "Grad D"
},
{
"content": "Well , as I say there is this s set of people next door , it 's not hard to",
"speaker": "Professor B"
},
{
"content": "We 're already {disfmarker} Yeah .",
"speaker": "Grad D"
},
{
"content": "uh {disfmarker}",
"speaker": "Professor B"
},
{
"content": "However , we may run into a problem with a reading task there . And um , we 'll see .",
"speaker": "Grad D"
},
{
"content": "Yeah . We could talk to the people who run it and um see if they have a way that they could easily uh tell people that there 's a task , pays ten bucks or something ,",
"speaker": "Professor B"
},
{
"content": "Mm - hmm . Yeah .",
"speaker": "Grad D"
},
{
"content": "but um you have to be comfortable reading relatively complicated stuff . And {disfmarker} and there 'll probably be self - selection to some extent .",
"speaker": "Professor B"
},
{
"content": "Mmm . Yep .",
"speaker": "Grad D"
},
{
"content": "Uh , so that 's good . Um . Now , {pause} I signed us up for the Wednesday slot , and part of what we should do is this .",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad D"
},
{
"content": "So , my idea on that was {pause} uh , partly we 'll talk about system stuff for the computer scientists , but partly I did want it to get the linguists involved in some of this issue about what the task is and all {disfmarker} um you know , what the dialogue is , and what 's going on linguistically , because to the extent that we can get them contributing , that will be good . So this issue about you know re - formulating things ,",
"speaker": "Professor B"
},
{
"content": "Yep .",
"speaker": "Grad D"
},
{
"content": "maybe we can get some of the linguists sufficiently interested that they 'll help us with it , uh , other linguists , if you 're a linguist , but in any case ,",
"speaker": "Professor B"
},
{
"content": "Yep .",
"speaker": "Grad D"
},
{
"content": "um , the linguistics students and stuff . So my idea on {disfmarker} on Wednesday is partly to uh {disfmarker} you {disfmarker} I mean , what you did today would {disfmarker} i is just fine . You just uh do \" this is what we did , and here 's the {pause} thing , and here 's s some of the dialogue and {disfmarker} and so forth . \" But then , the other thing of course is we should um give the computer scientists some idea of {disfmarker} of what 's going on with the system design , and where we think the belief - nets fit in and where the pieces are and stuff like that . Is {disfmarker} is this {pause} make sense to everybody ?",
"speaker": "Professor B"
},
{
"content": "Yep .",
"speaker": "Grad D"
},
{
"content": "Yeah . So , I don't {disfmarker} I don't think it 's worth a lot of work , particularly on your part , to {disfmarker} to {disfmarker} to make a big presentation . I don't think you should {disfmarker} you don't have to make any new {pause} uh PowerPoint or anything . I think we got plenty of stuff to talk about . And , then um just see how a discussion goes .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm . Sounds good . The uh other two things is um we 've {disfmarker} can have Johno tell us a little about this",
"speaker": "Grad D"
},
{
"content": "Great .",
"speaker": "Professor B"
},
{
"content": "and we also have a l little bit on the interface , M - three - L enhancement , and then um that was it , I think .",
"speaker": "Grad D"
},
{
"content": "So , what I did for this {disfmarker} this is {disfmarker} uh , a pedagogical belief - net because I was {disfmarker} I {disfmarker} I took {disfmarker} I tried to conceptually do what you were talking about with the nodes that you could expand out {disfmarker} so what I did was I took {disfmarker} I made these dummy nodes called Trajector - In and Trajector - Out that would isolate the things related to the trajector .",
"speaker": "Grad A"
},
{
"content": "Yep .",
"speaker": "Professor B"
},
{
"content": "And then there were the things with the source and the path and the goal .",
"speaker": "Grad A"
},
{
"content": "Yep .",
"speaker": "Professor B"
},
{
"content": "And I separated them out . And then I um did similar things for our {disfmarker} our net to {disfmarker} uh with the context and the discourse and whatnot , um , so we could sort of isolate them or whatever in terms of the {disfmarker} the top layer .",
"speaker": "Grad A"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "And then the bottom layer is just the Mode . So .",
"speaker": "Grad A"
},
{
"content": "So , let 's {disfmarker} let 's {disfmarker} Yeah , I don't understand it . Let 's go {disfmarker} Slide all the way up so we see what the p the p very bottom looks like , or is that it ?",
"speaker": "Professor B"
},
{
"content": "Yeah , there 's just one more node and it says \" Mode \" which is the decision between the {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Yeah .",
"speaker": "Grad D"
},
{
"content": "OK , great . Alright .",
"speaker": "Professor B"
},
{
"content": "So basically all I did was I took the last {pause} belief - net",
"speaker": "Grad A"
},
{
"content": "So {disfmarker} Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "and I grouped things according to what {disfmarker} how I thought they would fit in to uh image schemas that would be related . And the two that I came up with were Trajector - landmark and then Source - path - goal as initial ones .",
"speaker": "Grad A"
},
{
"content": "Yep . Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "And then I said well , uh the trajector would be the person in this case probably .",
"speaker": "Grad A"
},
{
"content": "Right , yep .",
"speaker": "Professor B"
},
{
"content": "Um , you know , we have {disfmarker} we have the concept of what their intention was , whether they were trying to tour or do business or whatever ,",
"speaker": "Grad A"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "or they were hurried . That 's kind of related to that . And then um in terms of the source , the things {disfmarker} uh the only things that we had on there I believe were whether {disfmarker} Oh actually , I kind of , {disfmarker} I might have added these cuz I don't think we talked too much about the source in the old one but uh whether the {disfmarker} where I 'm currently at is a landmark might have a bearing on whether {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "or the \" landmark - iness \" of where I 'm currently at . And \" usefulness \" is basi basically means is that an institutional facility like a town hall or something like that that 's not {disfmarker} something that you 'd visit for tourist 's {disfmarker} tourism 's sake or whatever . \" Travel constraints \" would be something like you know , maybe they said they can {disfmarker} they only wanna take a bus or something like that , right ? And then those are somewhat related to the path ,",
"speaker": "Grad A"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "so that would determine whether we 'd {disfmarker} could take {disfmarker} we would be telling them to go to the bus stop or versus walking there directly . Um , \" Goal \" . Similar things as the source except they also added whether the entity was closed and whether they have somehow marked that is was the final destination . Um , and then if you go up , Robert , Yeah , so {disfmarker} um , in terms of Context , what we had currently said was whether they were a businessman or a tourist of some other person . Um , Discourse was related to whether they had asked about open hours or whether they asked about where the entrance was or the admission fee , or something along those lines .",
"speaker": "Grad A"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "Uh , Prosody I don't really {disfmarker} I 'm not really sure what prosody means , in this context , so I just made up you know whether {disfmarker} whether what they say is {disfmarker} or h how they say it is {disfmarker} is that .",
"speaker": "Grad A"
},
{
"content": "Right , OK .",
"speaker": "Professor B"
},
{
"content": "Um , the Parse would be what verb they chose , and then maybe how they modified it , in the sense of whether they said \" I need to get there quickly \" or whatever .",
"speaker": "Grad A"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "And um , in terms of World Knowledge , this would just basically be like opening and closing times of things , the time of day it is , and whatnot .",
"speaker": "Grad A"
},
{
"content": "What 's \" tourbook \" ?",
"speaker": "Grad D"
},
{
"content": "Tourbook ? That would be , I don't know , the \" landmark - iness \" of things ,",
"speaker": "Grad A"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "whether it 's in the tourbook or not .",
"speaker": "Grad A"
},
{
"content": "Ch - ch - ch - ch . Now . Alright , so I understand what 's {disfmarker} what you got . I don't yet understand {pause} how you would use it . So let me see if I can ask",
"speaker": "Professor B"
},
{
"content": "Well , this is not a working Bayes - net .",
"speaker": "Grad A"
},
{
"content": "a s Right . No , I understand that , but {disfmarker} but um So , what {disfmarker} Let 's slide back up again and see {disfmarker} start at the {disfmarker} at the bottom and Oop - bo - doop - boop - boop . Yeah . So , you could imagine w Uh , go ahead , you were about to go up there and point to something .",
"speaker": "Professor B"
},
{
"content": "Well I {disfmarker} OK , I just {disfmarker} Say what you were gonna say .",
"speaker": "Grad A"
},
{
"content": "Good , do it !",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "No no , go do it .",
"speaker": "Professor B"
},
{
"content": "Uh {disfmarker} I {disfmarker} I 'd {disfmarker} No , I was gonna wait until {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Oh , OK . So , so if you {disfmarker} if we made {disfmarker} if we wanted to make it into a {disfmarker} a real uh Bayes - net , that is , you know , with fill {disfmarker} you know , actually f uh , fill it @ @ in , then uh {disfmarker}",
"speaker": "Professor B"
},
{
"content": "So we 'd have to get rid of this and connect these things directly to the Mode .",
"speaker": "Grad A"
},
{
"content": "Well , I don't {disfmarker} That 's an issue . So , um {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Cuz I don't understand how it would work otherwise .",
"speaker": "Grad A"
},
{
"content": "Well , here 's the problem . And {disfmarker} and uh {disfmarker} Bhaskara and I was talking about this a little earlier today {disfmarker} is , if we just do this , we could wind up with a huge uh , combinatoric input to the Mode thing . And uh {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Well I {disfmarker} oh yeah , I unders I understand that , I just {disfmarker} uh it 's hard for me to imagine how he could get around that .",
"speaker": "Grad A"
},
{
"content": "Well , i But that 's what we have to do .",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "OK , so , so , uh . There {disfmarker} there are a variety of ways of doing it . Uh . Let me just mention something that I don't want to pursue today which is there are technical ways of doing it , uh I I slipped a paper to Bhaskara and {disfmarker} about Noisy - OR 's and Noisy - MAXes and there 're ways to uh sort of back off on the purity of your Bayes - net - edness .",
"speaker": "Professor B"
},
{
"content": "Mmm .",
"speaker": "Grad A"
},
{
"content": "Uh , so . If you co you could ima and I now I don't know that any of those actually apply in this case , but there is some technology you could try to apply .",
"speaker": "Professor B"
},
{
"content": "So it 's possible that we could do something like a summary node of some sort that {disfmarker} OK .",
"speaker": "Grad A"
},
{
"content": "Yeah . Yeah . And , um So .",
"speaker": "Professor B"
},
{
"content": "So in that case , the sum we 'd have {disfmarker} we {disfmarker} I mean , these wouldn't be the summary nodes . We 'd have the summary nodes like where the things were {disfmarker} I guess maybe if thi if things were related to business or some other {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Yeah .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad A"
},
{
"content": "So what I was gonna say is {disfmarker} is maybe a good at this point is to try to informally {disfmarker} I mean , not necessarily in th in this meeting , but to try to informally think about what the decision variables are . So , if you have some bottom line uh decision about which mode , you know , what are the most relevant things .",
"speaker": "Professor B"
},
{
"content": "Mmm .",
"speaker": "Grad A"
},
{
"content": "And the other trick , which is not a technical trick , it 's kind of a knowledge engineering trick , is to make the n {pause} each node sufficiently narrow that you don't get this combinatorics . So that if you decided that you could characterize the decision as a trade - off between three factors , whatever they may be , OK ? then you could say \" Aha , let 's have these three factors \" , OK ? and maybe a binary version f for each , or some relatively compact decision node just above the final one .",
"speaker": "Professor B"
},
{
"content": "Mmm .",
"speaker": "Grad A"
},
{
"content": "And then the question would be if {disfmarker} if those are the things that you care about , uh can you make a relatively compact way of getting from the various inputs to the things you care about . So that y so that , you know , you can sort of try to do a knowledge engineering thing",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "given that we 're not gonna screw with the technology and just always use uh sort of orthodox Bayes - nets , then we have a knowledge engineering little problem of how do we do that . Um and",
"speaker": "Professor B"
},
{
"content": "So what I kind of need to do is to take this one and the old one and merge them together ?",
"speaker": "Grad A"
},
{
"content": "\" Eh - eh - eh . \" Yeah .",
"speaker": "Professor B"
},
{
"content": "So that {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Well , mmm , something . I mean , so uh , Robert has thought about this problem f for a long time , cuz he 's had these examples kicking around , so he may have some good intuition about you know , what are the crucial things .",
"speaker": "Professor B"
},
{
"content": "Mmm .",
"speaker": "Grad A"
},
{
"content": "and , um , I understand where this {disfmarker} the uh {disfmarker} this is a way of playing with this abs Source - path - goal trajector exp uh uh abstraction and {disfmarker} and sort of sh displaying it in a particular way .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad A"
},
{
"content": "Uh , I don't think our friends uh on Wednesday are going to be able to {disfmarker} Well , maybe they will . Well , let me think about whether {disfmarker} whether I think we can present this to them or not . Um , Uh ,",
"speaker": "Professor B"
},
{
"content": "Well , I think this is still , I mean , ad - hoc . This is sort of th the second {vocalsound} version and I {disfmarker} I {disfmarker} I {disfmarker} look at this maybe just as a , you know , a {disfmarker} a {disfmarker} whatever , UML diagram or , you know , as just a uh screen shot , not really as a Bayes - net as John {disfmarker} Johno said .",
"speaker": "Grad D"
},
{
"content": "We could actually , y yeah draw it in a different way , in the sense that it would make it more abstract .",
"speaker": "Grad A"
},
{
"content": "Yeah . But the uh {disfmarker} the {disfmarker} the nice thing is that you know , it just is a {disfmarker} is a visual aid for thinking about these things which has comple clearly have to be specified m more carefully",
"speaker": "Grad D"
},
{
"content": "Alright , well , le let me think about this some more ,",
"speaker": "Professor B"
},
{
"content": "and uh",
"speaker": "Grad D"
},
{
"content": "and uh see if we can find a way to present this to this linguists group that {disfmarker} that is helpful to them .",
"speaker": "Professor B"
},
{
"content": "I mean , ultimately we {disfmarker} we may w w we regard this as sort of an exercise in {disfmarker} in thinking about the problem and maybe a first version of uh a module , if you wanna call it that , that you can ask , that you can give input and it it 'll uh throw the dice for you , uh throw the die for you , because um I integrated this into the existing SmartKom system in {disfmarker} in the same way as much the same way we can um sort of have this uh {disfmarker} this thing . Close this down . So if this is what M - three - L um will look like and what it 'll give us , um {disfmarker} And a very simple thing . We have an action that he wants to go from somewhere , which is some type of object , to someplace .",
"speaker": "Grad D"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "And this {disfmarker} these uh {disfmarker} this changed now only um , um {disfmarker} It 's doing it twice now because it already did it once . Um , we 'll add some action type , which in this case is \" Approach \" and could be , you know , more refined uh in many ways .",
"speaker": "Grad D"
},
{
"content": "Mm - hmm . Good .",
"speaker": "Professor B"
},
{
"content": "Or we can uh have something where the uh goal is a public place and it will give us then of course an action type of the type \" Enter \" . So this is just based on this one {disfmarker} um , on this one feature , and that 's {disfmarker} that 's about all you can do . And so in the f if this pla if the object type um here is {disfmarker} is a m is a landmark , of course it 'll be um \" Vista \" . And um this is about as much as we can do if we don't w if we want to avoid uh uh a huge combinatorial explosion where we specify \" OK , if it 's this and this but that is not the case \" , and so forth , it just gets really really messy .",
"speaker": "Grad D"
},
{
"content": "OK , I 'm sorry . You 're {disfmarker} you 're {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Hmm ?",
"speaker": "Grad D"
},
{
"content": "It was much too quick for me . OK , so let me see if I understand what you 're saying . So , I {disfmarker} I do understand that uh you can take the M - three - L and add not {disfmarker} and it w and you need to do this , for sure , we have to add , you know , not too much about um object types and stuff , and what I think you did is add some rules of the style that are already there that say \" If it 's of type \" Landmark \" , then you take {disfmarker} you 're gonna take a picture of it . \"",
"speaker": "Professor B"
},
{
"content": "Exactly .",
"speaker": "Grad D"
},
{
"content": "F full stop , I mean , that 's what you do . Ev - every landmark you take a picture of ,",
"speaker": "Professor B"
},
{
"content": "Every public place you enter , and statue you want to go as near as possible .",
"speaker": "Grad D"
},
{
"content": "you enter {disfmarker} You approach . OK . Uh , and certainly you can add rules like that to the existing SmartKom system . And you just did , right ? OK .",
"speaker": "Professor B"
},
{
"content": "Yeah . And it {disfmarker} it would do us no good .",
"speaker": "Grad D"
},
{
"content": "Ah .",
"speaker": "Professor B"
},
{
"content": "That {disfmarker} Ultimately .",
"speaker": "Grad D"
},
{
"content": "Well . So , s well , and let 's think about this .",
"speaker": "Professor B"
},
{
"content": "W",
"speaker": "Grad D"
},
{
"content": "Um , that 's a {disfmarker} that 's another kind of baseline case , that 's another sort of thing \" OK , here 's a {disfmarker} another kind of minimal uh way of tackling this \" . Add extra properties , a deterministic rule for every property you have an action , \" pppt ! \" You do that . Um , then the question would be Uh Now , if that 's all you 're doing , then you can get the types from the ontology , OK ? because that 's all {disfmarker} you 're {disfmarker} all you 're using is this type {disfmarker} the types in the ontology and you 're done .",
"speaker": "Professor B"
},
{
"content": "Hmm ?",
"speaker": "Grad D"
},
{
"content": "Right ? So we don't {disfmarker} we don't use the discourse , we don't use the context , we don't do any of those things .",
"speaker": "Professor B"
},
{
"content": "No .",
"speaker": "Grad D"
},
{
"content": "Alright , but that 's {disfmarker} but that 's OK , and I mean it it 's again a kind of one minimal extension of the existing things . And that 's something the uh SmartKom people themselves would {disfmarker} they 'd say \" Sure , that 's no problem {disfmarker} you know , no problem to add types to the ont \" Right ?",
"speaker": "Professor B"
},
{
"content": "Yeah . No . And this is {disfmarker} just in order to exemplify what {disfmarker} what we can do very , very easily is , um we have this {disfmarker} this silly uh interface and we have the rules that are as banal as of we just saw , and we have our content .",
"speaker": "Grad D"
},
{
"content": "Hmm .",
"speaker": "Professor B"
},
{
"content": "Now , the content {disfmarker} I {disfmarker} whi which is sort of what {disfmarker} what we see here , which is sort of the Vista , Schema , Source , Path , Goal , whatever .",
"speaker": "Grad D"
},
{
"content": "Yeah . Yeah .",
"speaker": "Professor B"
},
{
"content": "This will um be um a job to find ways of writing down Image schema , X - schema , constructions , in some {disfmarker} some form , and have this be in a {disfmarker} in a {disfmarker} in the content , loosely called \" Constructicon \" . And the rules we want to throw away completely . And um {disfmarker} and here is exactly where what 's gonna be replaced with our Bayes - net , which is exactly getting the input feeding into here . This decides whether it 's an whether action {disfmarker} the {disfmarker} the Enter , the Vista , or the whatever",
"speaker": "Grad D"
},
{
"content": "Uh , \" approach \" , you called it , I think this time .",
"speaker": "Professor B"
},
{
"content": "uh Approach um construction should be activated , IE just pasted in .",
"speaker": "Grad D"
},
{
"content": "That 's what you said {disfmarker} Yeah , that 's fine . Yeah , but {disfmarker} Right . But it 's not construction there , it 's action . Construction is a d is a different story .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad D"
},
{
"content": "Right . This is uh {disfmarker} so what we 'd be generating would be a reference to a semantic uh like parameters for the {disfmarker} for the X - schema ?",
"speaker": "Grad A"
},
{
"content": "For {disfmarker} for {disfmarker} for {disfmarker} Yes .",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "Yeah . So that {disfmarker} that uh i if you had the generalized \" Go \" X - schema and you wanted to specialize it to these three ones , then you would have to supply the parameters .",
"speaker": "Professor B"
},
{
"content": "Right .",
"speaker": "Grad A"
},
{
"content": "And then uh , although we haven't worried about this yet , you might wanna worry about something that would go to the GIS and use that to actually get you know , detailed route planning . So , you know , where do you do take a picture of it and stuff like that .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm .",
"speaker": "Grad A"
},
{
"content": "But that 's not {disfmarker} It 's not the immediate problem .",
"speaker": "Professor B"
},
{
"content": "Right .",
"speaker": "Grad A"
},
{
"content": "But , presumably that {disfmarker} that {disfmarker} that functionality 's there when {disfmarker} when we {disfmarker}",
"speaker": "Professor B"
},
{
"content": "So the immediate problem is just deciding w which {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Aspects of the X - schema to add .",
"speaker": "Grad D"
},
{
"content": "Yeah , so the pro The immediate problem is {disfmarker} is back t t to what you were {disfmarker} what you are doing with the belief - net .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad A"
},
{
"content": "You know , uh what are we going to use to make this decision {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Right and then , once we 've made the decision , how do we put that into the content ?",
"speaker": "Grad A"
},
{
"content": "Yeah . Right . Right . Well , that {disfmarker} that actually is relatively easy in this case .",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "The harder problem is we decide what we want to use , how are we gonna get it ? And that the {disfmarker} the {disfmarker} that 's the hardest problem . So , the hardest problem is how are you going to get this information from some combination of the {disfmarker} what the person says and the context and the ontology . The h So , I think that 's the hardest problem at the moment is {disfmarker} is",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "where are you gonna {disfmarker} how are you gonna g get this information . Um , and that 's {disfmarker} so , getting back to here , uh , we have a d a technical problem with the belief - nets that we {disfmarker} we don't want all the com",
"speaker": "Professor B"
},
{
"content": "There 's just too many factors right now .",
"speaker": "Grad A"
},
{
"content": "too many factors if we {disfmarker} if we allow them to just go combinatorially .",
"speaker": "Professor B"
},
{
"content": "Right .",
"speaker": "Grad A"
},
{
"content": "So we wanna think about which ones we really care about and what they really most depend on , and can we c you know , clean this {disfmarker} this up to the point where it {disfmarker}",
"speaker": "Professor B"
},
{
"content": "So what we really wanna do i cuz this is really just the three layer net , we wanna b make it {disfmarker} expand it out into more layers basically ?",
"speaker": "Grad A"
},
{
"content": "Right . We might . Uh , I mean that {disfmarker} that 's certainly one thing we can do . Uh , it 's true that the way you have this , a lot of the times you have {disfmarker} what you 're having is the values rather than the variable . So uh {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Right . So instead of in instead it should really be {disfmarker} just be \" intention \" as a node instead of \" intention business \" or \" intention tour \" .",
"speaker": "Grad A"
},
{
"content": "OK ? So you {disfmarker} Yeah , right , and then it would have values , uh , \" Tour \" , \" Business \" , or uh \" Hurried \" .",
"speaker": "Professor B"
},
{
"content": "Right .",
"speaker": "Grad A"
},
{
"content": "But then {disfmarker} but i it still some knowledge design to do , about i how do you wanna break this up , what really matters .",
"speaker": "Professor B"
},
{
"content": "Right .",
"speaker": "Grad A"
},
{
"content": "I mean , it 's fine . You know , we have to {disfmarker} it 's {disfmarker} it 's iterative . We 're gonna have to work with it some .",
"speaker": "Professor B"
},
{
"content": "I think what was going through my mind when I did it was someone could both have a business intention and a touring intention and the probabilities of both of them happening at the same time {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Well , you {disfmarker} you could do that . And it 's perfectly OK {pause} to uh insist that {disfmarker} that , you know , th um , they add up to one , but that there 's uh {disfmarker} that {disfmarker} that it doesn't have to be one zero zero .",
"speaker": "Professor B"
},
{
"content": "Mmm . OK .",
"speaker": "Grad A"
},
{
"content": "OK . So you could have the conditional p So the {disfmarker} each of these things is gonna be a {disfmarker} a {disfmarker} a probability . So whenever there 's a choice , uh {disfmarker} so like landmark - ness and usefulness ,",
"speaker": "Professor B"
},
{
"content": "Well , see I don't think those would be mutually {disfmarker}",
"speaker": "Grad A"
},
{
"content": "OK {disfmarker}",
"speaker": "Professor B"
},
{
"content": "it seems like something could both be {disfmarker}",
"speaker": "Grad A"
},
{
"content": "Absolutely right .",
"speaker": "Professor B"
},
{
"content": "OK .",
"speaker": "Grad A"
},
{
"content": "And so that you might want to then have those b Th - Then they may have to be separate . They may not be able to be values of the same variable .",
"speaker": "Professor B"
},
{
"content": "Object type , mm - hmm .",
"speaker": "Grad D"
},
{
"content": "So that 's {disfmarker} but again , this is {disfmarker} this is the sort of knowledge design you have to go through . Right . It 's {disfmarker} you know , it 's great {disfmarker} is {disfmarker} is , you know , as one step toward uh {disfmarker} toward where we wanna go .",
"speaker": "Professor B"
},
{
"content": "Also it strikes me that we {disfmarker} we m may want to approach the point where we can sort of try to find a {disfmarker} uh , a specification for some interface , here that um takes the normal M - three - L , looks at it . Then we discussed in our pre - edu {disfmarker} EDU meeting um how to ask the ontology , what to ask the ontology um the fact that we can pretend we have one , make a dummy until we get the real one , and so um we {disfmarker} we may wanna decide we can do this from here , but we also could do it um you know if we have a {disfmarker} a {disfmarker} a belief - net interface . So the belief - net takes as input , a vector , right ? of stuff . And it {disfmarker} Yeah . And um it Output is whatever , as well . But this information is just M - three - L , and then we want to look up some more stuff in the ontology and we want to look up some more stuff in the {disfmarker} maybe we want to ask the real world , maybe you want to look something up in the GRS , but also we definitely want to look up in the dialogue history um some s some stuff . Based on we {disfmarker} we have uh {disfmarker} I was just made some examples from the ontology and so we have for example some information there that the town hall is both a {disfmarker} a {disfmarker} a building and it has doors and stuff like this , but it is also an institution , so it has a mayor and so forth and so forth and we get relations out of it and once we have them , we can use that information to look in the dialogue history , \" were any of these things that {disfmarker} that are part of the town hall as an institution mentioned ? \" ,",
"speaker": "Grad D"
},
{
"content": "Mm - hmm .",
"speaker": "Professor B"
},
{
"content": "\" were any of these that make the town hall a building mentioned ? \" ,",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "and so forth , and maybe draw some inferences on that . So this may be a {disfmarker} a sort of a process of two to three steps before we get our vector , that we feed into the belief - net ,",
"speaker": "Grad D"
},
{
"content": "Yeah . I think that 's {disfmarker} I think that 's exactly right .",
"speaker": "Professor B"
},
{
"content": "and then {disfmarker}",
"speaker": "Grad D"
},
{
"content": "There will be rules , but they aren't rules that come to final decisions , they 're rules that gather information for a decision process . Yeah ,",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad D"
},
{
"content": "no I think that 's {disfmarker} that 's just fine . Uh , yeah . So they 'll {disfmarker} they {disfmarker} presumably there 'll be a thread or process or something that \" Agent \" , yeah , \" Agent \" , whatever you wan wanna say , yeah , that uh is rule - driven , and can {disfmarker} can uh {disfmarker} can do things like that . And um there 's an issue about whether there will be {disfmarker} that 'll be the same agent and the one that then goes off and uh carries out the decision , so it probably will . My guess is it 'll be the same basic agent that um can go off and get information , run it through a {disfmarker} a c this belief - net that {disfmarker} turn a crank in the belief - net , that 'll come out with s uh more {disfmarker} another vector , OK , which can then be uh applied at what we would call the simulation or action end . So you now know what you 're gonna do and that may actually involve getting more information . So on once you pull that out , it could be that that says \" Ah ! Now that we know that we gonna go ask the ontology something else . \" OK ? Now that we know that it 's a bus trip , OK ? we didn't {disfmarker} We didn't need to know beforehand , uh how long the bus trip takes or whatever , but {disfmarker} but now that we know that 's the way it 's coming out then we gotta go find out more .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "So I think that 's OK .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm . So this is actually , s if {disfmarker} if we were to build something that is um , and , uh , I had one more thing , the {disfmarker} it needs to do {disfmarker} Yeah . I think we {disfmarker} I {disfmarker} I can come up with a {disfmarker} a code for a module that we call the \" cognitive dispatcher \" , which does nothing ,",
"speaker": "Grad D"
},
{
"content": "OK .",
"speaker": "Professor B"
},
{
"content": "but it looks of complect object trees and decides how {disfmarker} are there parts missing that need to be filled out , there 's {disfmarker} this is maybe something that this module can do , something that this module can do and then collect uh sub - objects and then recombine them and put them together . So maybe this is actually some {disfmarker} some useful tool that we can use to rewrite it , and uh get this part ,",
"speaker": "Grad D"
},
{
"content": "Oh , OK . Uh .",
"speaker": "Professor B"
},
{
"content": "then . Yeah .",
"speaker": "Grad D"
},
{
"content": "I confess , I 'm still not completely comfortable with the overall story . Um . I i This {disfmarker} this is not a complaint , this is a promise to do more work . So I 'm gonna hafta think about it some more . Um . In particular {disfmarker} see what we 'd like to do , and {disfmarker} and this has been implicit in the discussion , is to do this in such a way that you get a lot of re - use . So . What you 're trying to get out of this deep co cognitive linguistics is the fact that w if you know about source {disfmarker} source , paths and goals , and nnn {comment} all this sort of stuff , that a lot of this is the same , for different tasks . And that {disfmarker} uh there 's {disfmarker} there 's some {disfmarker} some important generalities that you 're getting , so that you don't take each and every one of these tasks and hafta re - do it . And I don't yet see how that goes . Alright .",
"speaker": "Professor B"
},
{
"content": "There 're no primitives upon which {pause} uh",
"speaker": "Grad D"
},
{
"content": "u u What are the primitives , and how do you break this {disfmarker}",
"speaker": "Professor B"
},
{
"content": "yeah .",
"speaker": "Grad D"
},
{
"content": "So I y I 'm just {disfmarker} just there saying eee {comment} well you {disfmarker} I know how to do any individual case , right ? but I don't yet {disfmarker} see what 's the really interesting question is can you use uh deep uh cognitive linguistics to {pause} get powerful generalizations . And",
"speaker": "Professor B"
},
{
"content": "Yep .",
"speaker": "Grad D"
},
{
"content": "um",
"speaker": "Professor B"
},
{
"content": "Maybe we sho should we a add then the \" what 's this ? \" domain ? N I mean , we have to \" how do I get to X \" . Then we also have the \" what 's this ? \" domain , where we get some slightly different {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Could . Uh .",
"speaker": "Professor B"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "Um Johno , actually , does not allow us to call them \" intentions \" anymore .",
"speaker": "Grad D"
},
{
"content": "Yeah .",
"speaker": "Professor B"
},
{
"content": "So he {disfmarker} he dislikes the term .",
"speaker": "Grad D"
},
{
"content": "Well , I {disfmarker} I don't like the term either , so I have n i uh i i y w i i It uh {disfmarker}",
"speaker": "Professor B"
},
{
"content": "But um , I 'm sure the \" what 's this ? \" questions also create some interesting X - schema aspects .",
"speaker": "Grad D"
},
{
"content": "Could be . I 'm not a {disfmarker} I 'm not op particularly opposed to adding that or any other task ,",
"speaker": "Professor B"
},
{
"content": "So .",
"speaker": "Grad D"
},
{
"content": "I mean , eventually we 're gonna want a whole range of them .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "Uh ,",
"speaker": "Professor B"
},
{
"content": "That 's right .",
"speaker": "Grad C"
},
{
"content": "I 'm just saying that I 'm gonna hafta do some sort of first principles thinking about this . I just at the moment don't know .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "H No . Well , no the Bayes {disfmarker} the Bayes - nets {disfmarker} The Bayes - nets will be dec specific for each decision . But what I 'd like to be able to do is to have the way that you extract properties , that will go into different Bayes - nets , be the {disfmarker} uh general . So that if you have sources , you have trajectors and stuff like that , and there 's a language for talking about trajectors , you shouldn't have to do that differently for uh uh going to something , than for circling it , for uh telling someone else how to go there ,",
"speaker": "Professor B"
},
{
"content": "Getting out of {disfmarker}",
"speaker": "Grad D"
},
{
"content": "whatever it is . So that {disfmarker} that , the {disfmarker} the decision processes are gonna be different What you 'd really like of course is the same thing you 'd always like which is that you have um a kind of intermediate representation which looks the same o over a bunch of inputs and a bunch of outputs . So all sorts of different tasks {pause} and all sorts of different ways of expressing them use a lot of the same mechanism for pulling out what are the fundamental things going on . And that 's {disfmarker} that would be the really pretty result . And pushing it one step further , when you get to construction grammar and stuff , what you 'd like to be able to do is say you have this parser which is much fancier than the parser that comes with uh SmartKom , i that {disfmarker} that actually uses constructions and is able to tell from this construction that there 's uh something about the intent {disfmarker} you know , the actual what people wanna do or what they 're referring to and stuff , in independent of whether it {disfmarker} about {disfmarker} what is this or where is it or something , that you could tell from the construction , you could pull out deep semantic information which you 're gonna use in a general way . So that 's the {disfmarker} You might . You might . You might be able to {disfmarker} to uh say that this i this is the kind of construction in which the {disfmarker} there 's {disfmarker} Let 's say there 's a uh cont there {disfmarker} the {disfmarker} the land the construction implies the there 's a con this thing is being viewed as a container . OK . So just from this local construction you know that you 're gonna hafta treat it as a container you might as well go off and get that information . And that may effect the way you process everything else . So if you say \" how do I get into the castle \" OK , then um {disfmarker} Or , you know , \" what is there in the castle \" or {disfmarker} so there 's all sorts of things you might ask that involve the castle as a container and you 'd like to have this orthogonal so that anytime the castle 's referred to as a container , you crank up the appropriate stuff . Independent of what the goal is , and independent of what the surrounding language is .",
"speaker": "Professor B"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "Alright , so that 's {disfmarker} that 's the {disfmarker} that 's the thesis level",
"speaker": "Professor B"
},
{
"content": "Mm - hmm .",
"speaker": "Grad D"
},
{
"content": "uh {disfmarker}",
"speaker": "Professor B"
},
{
"content": "It 's unfortunate also that English has sort of got rid of most of its spatial adverbs because they 're really fancy then , in {disfmarker} in {disfmarker} for these kinds of analysis . But uh .",
"speaker": "Grad D"
},
{
"content": "Well , you have prepositional phrases that {disfmarker}",
"speaker": "Professor B"
},
{
"content": "Yeah , but they 're {disfmarker} they 're easier for parsers .",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "Parsers can pick those up but {disfmarker} but the {disfmarker} with the spatial adverbs , they have a tough time . Because the {disfmarker} mean the semantics are very complex in that .",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "OK , yeah ? I had one more {pause} thing . I don't remember . I just forgot it again . No . Oh yeah , b But an architecture like this would also enable us maybe to {disfmarker} to throw this away and {disfmarker} and replace it with something else , or whatever , so that we have {disfmarker} so that this is sort of the representational formats we 're {disfmarker} we 're {disfmarker} we 're talking about that are independent of the problem , that generalize over those problems , and are oh , t of a higher quality than an any actual whatever um belief - net , or \" X \" that we may use for the decision making , ultimately . Should be decoupled , yeah . OK .",
"speaker": "Grad D"
},
{
"content": "Right . So , are we gonna be meeting here from now on ? I 'm {disfmarker} I 'm happy to do that . We {disfmarker} we had talked about it , cuz you have th th the display and everything , that seems fine .",
"speaker": "Professor B"
},
{
"content": "Yeah , um , Liz also asks whether we 're gonna have presentations every time . I don't think we will need to do that but it 's {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "so far I think it was nice as a visual aid for some things and {disfmarker} and {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Oh yeah . No I {disfmarker} I think it 's worth it to ass to meet here to bring this , and assume that something may come up that we wanna look at .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad D"
},
{
"content": "I mean . Why not .",
"speaker": "Professor B"
},
{
"content": "And um . Yeah , that was my {disfmarker}",
"speaker": "Grad D"
},
{
"content": "She was good . Litonya was good .",
"speaker": "Professor B"
},
{
"content": "Yeah ? The uh {disfmarker} um , she w she was definitely good in the sense that she {disfmarker} she showed us some of the weaknesses",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Professor B"
},
{
"content": "and um also the um {disfmarker} {vocalsound} the fact that she was a real subject you know , is {disfmarker} is {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Right . Yeah , and {disfmarker} and {disfmarker} and {disfmarker} yeah and {disfmarker} and she took it seriously and stuff l No , it was great .",
"speaker": "Professor B"
},
{
"content": "Yeah .",
"speaker": "Grad D"
},
{
"content": "Yeah .",
"speaker": "Professor B"
},
{
"content": "So I think that um {disfmarker} I mean , w Looking {disfmarker} just looking at this data , listening to it , what can we get out of it in terms of our problem , for example , is , you know , she actually m said {disfmarker} you know , she never s just spoke about entering , she just wanted to get someplace , and she said for buying stuff . Nuh ? So this is definitely interesting , and {disfmarker}",
"speaker": "Grad D"
},
{
"content": "Yeah , right .",
"speaker": "Grad C"
},
{
"content": "Um , and in the other case , where she wanted to look at the stuff at the graffiti , also , of course , not in the sentence \" How do you get there ? \" was pretty standard . Nuh ? except that there was a nice anaphora , you know , for pointing at what she talked about before , and there she was talking about looking at pictures that are painted inside a wall on walls , so",
"speaker": "Grad D"
},
{
"content": "Right .",
"speaker": "Grad C"
},
{
"content": "Actually , you 'd need a lot of world knowledge . This would have been a classical um uh \" Tango \" , actually . Um , because graffiti is usually found on the outside and not on the inside ,",
"speaker": "Grad D"
},
{
"content": "Yeah .",
"speaker": "Grad C"
},
{
"content": "but OK . So the mistake {comment} would have make a mistake {disfmarker} the system would have made a mistake here .",
"speaker": "Grad D"
},
{
"content": "Yep .",
"speaker": "Grad C"
},
{
"content": "Click ? Alright .",
"speaker": "Professor B"
}
] |
Bed005
| [{"relevant_text_span":[["1","39"]],"topic":"Data collection"},{"relevant_text_span":[["40","184"]],(...TRUNCATED)
| [{"answer":"The meeting discussed various topics such as data collection and updates on the German p(...TRUNCATED)
| [{"answer":"The actual number of the inputs in the Bayes-net can create a combinatorial explosion wh(...TRUNCATED)
| [{"content":"Yeah , I think I got my mike on . OK . Let 's see .","speaker":"Grad A"},{"content":"OK(...TRUNCATED)
|
Bed006
| [{"relevant_text_span":[["23","160"]],"topic":"Introducing Fey and discussing participant recruitmen(...TRUNCATED)
| [{"answer":"Meeting participants began by going over the logistics of recruiting participants, parti(...TRUNCATED)
| [{"answer":"The new system for collecting subject intention focused on allowing subjects to come up (...TRUNCATED)
| [{"content":"Time .","speaker":"Grad G"},{"content":"Thanks .","speaker":"Grad C"},{"content":"Are y(...TRUNCATED)
|
Bed009
| [{"relevant_text_span":[["0","119"]],"topic":"SmartKom architecture"},{"relevant_text_span":[["120",(...TRUNCATED)
| [{"answer":"The group discussed plans and concerns regarding the architecture of SmartKom, its propo(...TRUNCATED)
| [{"answer":"It was decided that SmartKom's action plans should be represented in XML as a state tran(...TRUNCATED)
| [{"content":"Hmm . Testing channel two .","speaker":"Grad C"},{"content":"Two , two . ","speaker":"G(...TRUNCATED)
|
Bed011
| [{"relevant_text_span":[["290","350"]],"topic":"Structure of the belief-net"},{"relevant_text_span":(...TRUNCATED)
| [{"answer":"The main focus of the meeting was firstly on the structure of the belief-net, its decisi(...TRUNCATED)
| [{"answer":"The team discussed that the organisation of the intermediate nodes of the belief-net and(...TRUNCATED)
| [{"content":"Now can you give me the uh {pause} remote T ?","speaker":"Grad C"},{"content":"OK , so (...TRUNCATED)
|
Bed012
| [{"relevant_text_span":[["0","100"]],"topic":"Presentation of work done"},{"relevant_text_span":[["1(...TRUNCATED)
| [{"answer":"The focus of the meeting was on a presentation of the work done already on the building (...TRUNCATED)
| [{"answer":"The input layer deriving information from things like the user and situation models, fee(...TRUNCATED)
| [{"content":"So I guess this is more or less now just to get you up to date , Johno . This is what ,(...TRUNCATED)
|
Bed013
| [{"relevant_text_span":[["0","160"]],"topic":"Future work"},{"relevant_text_span":[["161","441"]],"t(...TRUNCATED)
| [{"answer":"An idea for future work was suggested during the visit of the german project manager: th(...TRUNCATED)
| [{"answer":"An idea for future work was suggested during the visit of the german project manager: th(...TRUNCATED)
| [{"content":"As usual .","speaker":"Grad E"},{"content":"Yes . Whew ! I almost forgot {pause} about (...TRUNCATED)
|
Bed014
| [{"relevant_text_span":[["0","61"]],"topic":"Minor technical issues"},{"relevant_text_span":[["62","(...TRUNCATED)
| [{"answer":"Several technical matters are being resolved: a conversion program is being written for (...TRUNCATED)
| [{"answer":"For the SmartKom generation module, all the syntax-to-prosody rules are going to be re-w(...TRUNCATED)
| [{"content":"Sorry . Mental {disfmarker} mental Palm Pilot . Right . Hence {pause} no problem .","sp(...TRUNCATED)
|
Bed017
| [{"relevant_text_span":[["0","48"]],"topic":"Current progress with data and wizard"},{"relevant_text(...TRUNCATED)
| [{"answer":"The first phase of the data collection has finished. There is a new wizard for phase two(...TRUNCATED)
| [{"answer":"The first phase of the data collection has finished. There is a new wizard for phase two(...TRUNCATED)
| [{"content":"Why ?","speaker":"Grad A"},{"content":"Um .","speaker":"Grad D"},{"content":"I 'm known(...TRUNCATED)
|
End of preview. Expand
in Data Studio
README.md exists but content is empty.
- Downloads last month
- -