[speaker003:] Hmm. Testing channel two.
[speaker005:] Two, two.
[speaker003:] Two.
[speaker005:] Two. Oh.
[speaker004:] Hello?
[speaker002:] Hmm? Yeah Thank You. OK Well, so Ralf and Tilman are here.
[speaker006:] OK. Great. Great.
[speaker002:] Made it safely.
[speaker006:] So the [disfmarker] what w we h have been doing i they would like us all to read these digits. But we don't all read them but a couple people read them.
[speaker001:] OK.
[speaker006:] Uh, wanna give them all with German accents today or [disfmarker]?
[speaker002:] Sure.
[speaker006:] OK.
[speaker002:] OK and the way you do it is you just read the numbers not as uh each single, so just like I do it.
[speaker001:] Mm hmm.
[speaker002:] OK. First you read the transcript number.
[speaker004:] OK,
[speaker002:] Turn.
[speaker004:] uh [disfmarker] What's [disfmarker]
[speaker006:] OK. Let's be done with this. OK.
[speaker001:] OK.
[speaker006:] this is Ami, who [disfmarker] And this is Tilman and Ralf.
[speaker001:] Hi. Uh huh. Nice to meet you.
[speaker004:] Hi.
[speaker006:] Hi. OK. So we're gonna try to finish by five so people who want to can go hear Nancy Chang's talk, uh downstairs.
[speaker001:] Hmm.
[speaker006:] And you guys are g giving talks on tomorrow and Wednesday lunch times,
[speaker001:] Yes.
[speaker004:] Mmm.
[speaker006:] right? That's great. OK so, do y do you know what we're gonna do?
[speaker002:] I thought two things uh we'll introduce ourselves and what we do. And um we already talked with Andreas, Thilo and David and some lines of code were already written today and almost tested and just gonna say we have um again the recognizer to parser thing where we're working on and that should be no problem and then that can be sort of developed uh as needed when we get [disfmarker] enter the tourism domain. em we have talked this morning with the [disfmarker] with Tilman about the generator. and um There one of our diligent workers has to sort of volunteer to look over Tilman's shoulder while he is changing the grammars to English
[speaker001:] S Mm hmm.
[speaker002:] because w we have [disfmarker] we face two ways. Either we do a syllable concatenating um grammar for the English generation which is sort of starting from scratch and doing it the easy way, or we simply adopt the ah um more in depth um style that is implemented in the German system and um are then able not only to produce strings but also the syntactic parse uh not parse not the syntactic tree that is underneath in the syntactic structure which is the way we decided we were gonna go because A, it's easier in the beginning
[speaker001:] Mm hmm.
[speaker002:] and um it does require some [disfmarker] some knowledge of [disfmarker] of those grammars and [disfmarker] and [disfmarker] and some ling linguistic background. But um it shouldn't be a problem for anyone.
[speaker006:] OK So That sounds good. Johno, are you gonna have some time t to do that uh w with these guys?
[speaker005:] Sure.
[speaker006:] cuz y you're the grammar maven.
[speaker005:] OK.
[speaker006:] I mean it makes sense, doesn't it?
[speaker005:] Yeah.
[speaker006:] Yeah Good. OK. So, I think that's probably the [disfmarker] the right way to do that. And an Yeah, so I [disfmarker] I actually wanna f to find out about it too, but I may not have time to get in.
[speaker002:] the [disfmarker] the ultimate goal is that before they leave we [disfmarker] we can run through the entire system input through output on at least one or two sample things. And um and by virtue of doing that then in this case Johno will have acquired the knowledge of how to extend it. Ad infinitum. When needed, if needed, when wanted and so forth.
[speaker006:] OK that sounds great.
[speaker002:] And um also um Ralf has hooked up with David and you're gonna continue either all through tonight or tomorrow on whatever to get the er parser interface working.
[speaker004:] Mmm.
[speaker002:] They are thinning out and thickening out lattices and doing this kind of stuff to see what works best.
[speaker004:] Mmm, yep.
[speaker006:] Great. So, you guys enjoy your weekend?
[speaker001:] Yes, very much so.
[speaker004:] Yeah, very much
[speaker006:] OK, before [disfmarker] before you got put to work?
[speaker004:] Yeah
[speaker006:] Great. OK, so that's [disfmarker] Sort of one branch is to get us caught up on what's going on. Also of course it would be really nice to know what the plans are, in addition to what's sort of already in code.
[speaker001:] Yes.
[speaker006:] and we can d I dunno w w was there uh a time when we were set up to do that? It probably will work better if we do it later in the week, after [pause] we actually understand uh better what's going on.
[speaker001:] Yes.
[speaker004:] Hmm.
[speaker001:] Yeah.
[speaker006:] So when do you guys leave?
[speaker001:] Um we're here through Sunday,
[speaker004:] Oh
[speaker001:] so
[speaker006:] Oh, OK,
[speaker001:] All through Friday would be fine.
[speaker006:] so [disfmarker] OK, So [disfmarker] so anyt we'll find a time later in the week to uh get together and talk about [pause] your understanding of what SmartKom plans are.
[speaker001:] Mm hmm.
[speaker006:] and how we can change them.
[speaker001:] Yes. Sure.
[speaker006:] Uh,
[speaker002:] Should we already set a date for that? Might be beneficial while we're all here.
[speaker006:] OK? um What [disfmarker] what does not work for me is Thursday afternoon. I can do earlier in the day on Thursday, or [pause] um [pause] most of the time on Friday, not all.
[speaker002:] Thursday morning sounds fine?
[speaker006:] Wha but, Johno,
[speaker001:] Mm hmm.
[speaker006:] what are your constraints?
[speaker005:] um Thursday afternoon doesn't work for me, but [disfmarker]
[speaker002:] Neither does Thursday morning, no?
[speaker005:] Uh Thursday morning should be fine.
[speaker006:] Eleven?
[speaker001:] OK.
[speaker006:] Eleven on Thursday?
[speaker005:] I was just thinking I w I will [pause] have [pause] leavened by eleven.
[speaker006:] Right. Right. This is then out of deference to our non morning people.
[speaker001:] Mm hmm. OK. So at eleven?
[speaker004:] Hmm.
[speaker001:] Thursday around eleven? OK.
[speaker006:] Yeah. And actually we can invite um Andreas as well.
[speaker002:] Uh he will be in Washington, though.
[speaker006:] Oh that's true. He's off [disfmarker] off on his trip already.
[speaker002:] but um David is here and he's actually knows everything about the SmartKom recognizer.
[speaker006:] Thilo. OK well yeah maybe we'll see if David could make it. That would be good.
[speaker002:] OK so facing to [disfmarker] to what we've sort of been doing here um well for one thing we're also using this room to collect data.
[speaker001:] Yeah obviously.
[speaker002:] um um Not this type of data, no not meeting data but sort of [disfmarker] sort ah our version of a wizard experiment such
[speaker001:] Oh, OK.
[speaker002:] not like the ones in Munich but pretty close to it.
[speaker001:] Mm hmm.
[speaker002:] The major difference to the Munich ones is that we do it via the telephone
[speaker001:] OK.
[speaker002:] even though all the recording is done here and so it's a [disfmarker] sort of a computer call system that gives you tourist information
[speaker001:] Mm hmm.
[speaker002:] tells you how to get places. And it breaks halfway through the experiment and a human operator comes on. and part of that is sort of trying to find out whether people change their linguistic verbal behavior when first thinking they speak to a machine and then to a human.
[speaker001:] Yeah.
[speaker002:] and we're setting it up so that we can [disfmarker] we hope to implant certain intentions in people. For example um we have first looked at a simple sentence that "How do I get to the Powder Tower?" OK so you have the [disfmarker] castle of Heidelberg
[speaker001:] OK.
[speaker002:] and there is a tower and it's called Powder Tower.
[speaker001:] Oh, OK. Yeah.
[speaker002:] and um so What will you parse out of that sentence? Probably something that we specified in M three L,
[speaker004:] Mmm.
[speaker002:] that is [@ @] [comment] "action go to whatever domain, object whatever Powder Tower". And maybe some model will tell us, some GPS module, in the mobile scenario where the person is at the moment. And um we've sort of gone through that once before in the Deep Mail project and we noticed that first of all what are [disfmarker] I should've brought some slides, but what our [disfmarker] So here's the tower. Think of this as a two dimensional representation of the tower. And our system led people here, to a point where they were facing a wall in front of the tower. There is no entrance there, but it just happens to be the closest point of the road network to the geometric center Because that's how the algorithm works. So we took out that part of the road network as a hack and then it found actually the way to the entrance. which was now the closest point of the road network to
[speaker001:] Yeah.
[speaker002:] OK, geometric center. But what we actually observed in Heidelberg is that most people when they want to go there they actually don't want to enter, because it's not really interesting. They wanna go to a completely different point where they can look at it and take a picture.
[speaker001:] Oh, OK.
[speaker004:] Hmm.
[speaker001:] Yeah.
[speaker002:] And so what uh uh a s you s let's say a simple parse from a s from an utterance won't really give us is what the person actually wants. Does he wanna go there to see it? Does he wanna go there now? Later? How does the person wanna go there? Is that person more likely to want to walk there? Walk a scenic route? and so forth. There are all kinds of decisions that we have identified in terms of getting to places and in terms of finding information about things. And we are constructing [disfmarker] and then we've identified more or less the extra linguistic parameters that may f play a role. Information related to the user and information related to the situation. And we also want to look closely on the linguistic information that what we can get from the utterance. That's part of why we implant these intentions in the data collection to see whether people actually phrase things differently whether they want to enter in order to buy something or whether they just wanna go there to look at it. And um so the idea is to construct uh um suitable interfaces and a belief net for a module that actually tries to guess what the underlying intention [pause] was. And then enrich or augment the M three L structures with what it thought what more it sort of got out of that utterance. So if it can make a good suggestion, "Hey!" you know, "that person doesn't wanna enter. That person just wants to take a picture," cuz he just bought film, or "that person wants to enter because he discussed the admission fee before". Or "that person wants to enter because he wants to buy something and that you usually do inside of buildings" and so forth. These ah these types of uh these bits of additional information are going to be embedded into the M three L structure in an [disfmarker] sort of subfield that we have reserved. And if the action planner does something with it, great. If not you know, then that's also something um that we can't really [disfmarker] at least we [comment] want to offer the extra information. We don't really [disfmarker] um we're not too worried.
[speaker001:] Mm hmm.
[speaker004:] Hmm.
[speaker002:] I mean [disfmarker] t s Ultimately if you have [disfmarker] if you can offer that information, somebody's gonna s do something with it sooner or later. That's sort of part of our belief.
[speaker005:] What was he saying?
[speaker002:] Um, for example, right now I know the GIS from email is not able to calculate these viewpoints. So that's a functionality that doesn't exist yet to do that dynamically,
[speaker001:] Mm hmm.
[speaker002:] but if we can offer it that distinction, maybe somebody will go ahead and implement it. Surely nobody's gonna go ahead and implement it if it's never gonna be used, so. What have I forgotten about? Oh yeah,
[speaker006:] Well th uh
[speaker002:] how we do it, yeah that's the
[speaker006:] No no. It's a good time to pause. I s I see [pause] questions on peoples' faces, so why don't [disfmarker] let's [disfmarker] let's [disfmarker] Let's hear [disfmarker]
[speaker001:] Oh Well the obvious one would be if [disfmarker] if you envision this as a module within SmartKom, where exactly would that Sit?
[speaker002:] um [disfmarker] so far I've thought of it as sort of adding it onto the modeler knowledge module.
[speaker001:] That's the d
[speaker004:] Hmm.
[speaker001:] OK, yeah.
[speaker002:] So this is one that already adds additional information to the
[speaker001:] Makes perfect sense. Yes.
[speaker004:] Hmm, ah.
[speaker002:] but it could sit anywhere in the attention recognition I mean basically this is what attention recognition literally sort of can [disfmarker]
[speaker001:] Well it's supposed to do.
[speaker004:] Mmm.
[speaker001:] Yeah
[speaker006:] That's what it should do. Right, yeah.
[speaker001:] Yeah. Yeah.
[speaker004:] Huh.
[speaker002:] Yeah.
[speaker001:] Well f from my understanding of what the people at Phillips were originally trying to do doesn't seem to quite fit into SmartKom currently so what they're really doing right now is only selecting among the alternatives, the hypotheses that they're given enriched by the domain knowledge and the um discourse modeler and so on.
[speaker002:] Yeah. Yeah.
[speaker001:] So if [disfmarker] if this is additional information that could be merged in by them. And then it would be available to action planning and [disfmarker] and others.
[speaker002:] Yeah. the [disfmarker]
[speaker006:] let's [disfmarker] let's That w OK that was one question. Is there other [disfmarker] other things that cuz [pause] we wanna not Pa pass over any [pause] you know, questions or concerns that you have.
[speaker001:] Well there're [disfmarker] there're two levels of [disfmarker] of giving an answer and I guess on both levels I don't have any um further questions.
[speaker004:] Mmm. Mmm.
[speaker001:] uh the [disfmarker] the two levels will be as far as I'm concerned as [pause] uh standing here for the generation module
[speaker004:] Mmm.
[speaker001:] and the other is [disfmarker] is my understanding of what SmartKom uh is supposed to be
[speaker006:] Right.
[speaker001:] and I [disfmarker] I think that fits in perfectly
[speaker006:] So [disfmarker] well, let me [disfmarker] Let me s [pause] expand on that a little bit from the point of view of the generation.
[speaker004:] Hmm.
[speaker001:] Yeah.
[speaker006:] So the idea is that we've actually got this all laid out an and we could show it to you ig um Robert didn't bring it today but there's a [disfmarker] a belief net which is [disfmarker] There's a first cut at a belief net that [disfmarker] that doesn't [disfmarker] it [disfmarker] isn't fully uh instantiated, and in particular some of the [disfmarker] the combination rules and ways of getting the [disfmarker] the conditional probabilities aren't there. But we believe that we have laid out the fundamental decisions in this little space
[speaker001:] Mm hmm.
[speaker006:] and the things that influence them. So one of the decisions is what we call this AVE thing. Do you want to um access, view or enter a thing.
[speaker004:] Hmm.
[speaker006:] So that's a a discrete decision.
[speaker001:] Mm hmm.
[speaker006:] There are only three possibilities and the uh [disfmarker] what one would like is for this uh, knowledge modeling module to add which of those it is and give it to the planner.
[speaker001:] Mm hmm.
[speaker006:] But, uh th the current design suggests that if it seems to be an important decision and if the belief net is equivocal so that it doesn't say that one of these is much more probable than the other, then an option is to go back and ask for the information you want.
[speaker001:] Mm hmm.
[speaker006:] Alright? Now there are two ways one can go [disfmarker] a imagine doing that. For the debugging we'll probably just have a [disfmarker] a drop down menu and the [disfmarker] while you're debugging you will just [disfmarker] OK. But for a full system, then one might very well formulate a query, give it to the dialogue planner and say this, you know ar are you know you [disfmarker] are you planning to enter?
[speaker001:] Mm hmm.
[speaker006:] Or whatever it [disfmarker] whatever that might be. So that's [disfmarker] under that model then, There would be a [disfmarker] uh [disfmarker] um a loop in which this thing would formulate a query,
[speaker001:] Yes.
[speaker006:] presumably give it to you. That would get expressed and then hopefully you know, you'd get an answer [pause] back.
[speaker001:] Yep.
[speaker006:] And that would of course [disfmarker] the answer would have to be parsed.
[speaker004:] Mmm.
[speaker006:] right
[speaker004:] Yep.
[speaker006:] and [disfmarker] OK so, [pause] th [pause] that uh,
[speaker001:] Yes.
[speaker006:] We probably won't do this early on, because the current focus is more on the decision making and stuff like that.
[speaker001:] Yep.
[speaker006:] But While we're on the subject I just wanted to give you a sort of head's up that it could be that some months from now we said "OK we're now ready to try to close that loop" in terms of querying about some of these decisions.
[speaker001:] Mm hmm. Mm hmm.
[speaker004:] Hmm.
[speaker001:] Yep. So [disfmarker] my suggestion then is that you um look into the currently ongoing discussion about how the action plans are supposed to look like. And they're currently um Agreeing or [disfmarker] or in the process of agreeing on an X M L ification of um something like a state transition network of how dialogues would proceed. and [disfmarker] The [disfmarker] these um transition networks uh will be what the action planner interprets in a sense.
[speaker006:] Hmm. D did you know this Robert?
[speaker002:] uh Michael is doing that, right?
[speaker001:] Well uh Marcus Lerkult is actually implementing that stuff and Marcus and Michael together are um leading the discussion there,
[speaker002:] OK.
[speaker001:] yeah.
[speaker006:] So we ha we have to get in on that.
[speaker002:] Mm hmm.
[speaker001:] Yep.
[speaker006:] because um partly those are like X schemas.
[speaker004:] Mmm.
[speaker001:] Definitely.
[speaker006:] the transition diagrams.
[speaker002:] Hmm.
[speaker006:] And it may be that [disfmarker] that um we should early on make sure that they have the flexibility that we need.
[speaker002:] Hmm. But they uh Have I understood this right? They [disfmarker] they govern more or less the [disfmarker] the dialogue behavior or the action [disfmarker]
[speaker001:] Mm hmm.
[speaker002:] It's not really what you do with the content of the dialogue but it's So, I mean there is this [disfmarker] this [disfmarker] this nice interf
[speaker004:] uh, No, it's [disfmarker] it's also a quantrant uh uh [disfmarker]
[speaker002:] i Is it [disfmarker]
[speaker006:] So there's ac so there [disfmarker] th the word "action", OK, is [disfmarker] is what's ambiguous here.
[speaker004:] I think. Hmm.
[speaker001:] Yes.
[speaker006:] So, um one thing is there's an actual planner that tells the person in the tourist domain now, per tells the person how to go,
[speaker001:] OK.
[speaker006:] " First go here, first go there
[speaker004:] Mm hmm.
[speaker006:] uh, you know, take a bus ", whatever it is. So that's that form of planning, and action, and a route planner and GIS, all sort of stuff. uh But I think that isn't what you mean.
[speaker001:] No. No, in SmartKom terminology that's um called a function that's modeled by a function modeler. And it's th that's completely um encapsulated from th the dialogue system. That's simply a functionality that you give data as in a query and then you get back from that mmm, a functioning model um which might be a planner or a VCR or whatever. um some result and that's then [disfmarker] then used.
[speaker006:] Well, OK, so that's what I thought. So action he action here means dia uh speech ac uh you know dialogue act.
[speaker001:] Yeah, yeah.
[speaker002:] Mmm.
[speaker001:] Yeah, in that [disfmarker] in that sense yes,
[speaker006:] Yeah.
[speaker001:] dialogue act, yeah.
[speaker006:] Um, I think tha I think it's not going to [disfmarker] I think that's not going to be good enough. I I don what uh [disfmarker] what I meant by that. So I think the idea of having a, you know, transition diagram for the grammar of conversations is a good idea.
[speaker001:] Mm hmm.
[speaker006:] OK? And I think that we do hav definitely have to get in on it and find out [disfmarker] OK. But I think that um when [disfmarker] so, when you get to the tourist domain it's not just an information retrieval system.
[speaker001:] Mm hmm.
[speaker006:] Right?
[speaker001:] Clearly.
[speaker006:] So this i this is where I think this [disfmarker]
[speaker001:] Yes.
[speaker006:] people are gonna have to think this through a bit more carefully.
[speaker001:] Mm hmm.
[speaker006:] So, if it's only like in [disfmarker] in the [disfmarker] in the film and T V thing, OK, you can do this. And you just get information and give it to people. But what happens when you actually get them moving and so forth and so on
[speaker001:] Yep.
[speaker006:] Uh, y y your [disfmarker] I d I think the notion of this as a self contained uh module you know th the functional module that [disfmarker] that interacts with [disfmarker] with where the tourism g stuff is going [comment] probably is too restrictive.
[speaker001:] Yep.
[speaker006:] Now I dunno how much people have thought ahead to the tourist domain in this
[speaker001:] Probably not enough, I mean an [disfmarker] another uh more basic point there is that the current um tasks and therefore th the concepts in this ac what's called the action plan and what's really the dialogue manager.
[speaker006:] Yeah
[speaker001:] um is based on slots that have to be filled and the um kind of values in these slots would be fixed things like the a time or a movie title or something like this
[speaker006:] Mm hmm. Right.
[speaker001:] whereas in the a um tourist domain it might be an entire route.
[speaker006:] Indeed.
[speaker001:] Set based, or even very complex structured information in these slots
[speaker006:] Right.
[speaker001:] and I'm not sure if [disfmarker] if complex slots of that type are really um being taken into consideration.
[speaker006:] OK. Could you [disfmarker] could you put a message into the right place to see if we can at least ask that question?
[speaker001:] So that's [disfmarker] that's really something we
[speaker002:] Yep.
[speaker001:] Mm hmm.
[speaker002:] rea
[speaker001:] I mean nothing's being completely settled there
[speaker002:] yep
[speaker001:] so this is really an ongoing discussion
[speaker002:] Mm hmm yeah and um it might actually
[speaker001:] and that's
[speaker002:] OK ah also [disfmarker] because um again in in Deep Map we have faced and implemented those problems once already maybe we can even shuffle some know how from there to to Markus and Michael.
[speaker001:] Mm hmm. Yes.
[speaker004:] Mmm.
[speaker001:] Yep.
[speaker002:] And um mmm You don't know [disfmarker] OK th I'll [disfmarker] I'll talk to Michael it's what I do anyway. Who [disfmarker] How far is the uh the [disfmarker] the M three L specification for [disfmarker] for the la natural language input gone on the [disfmarker] the uh I haven't seen anything for the uh tourist path domain.
[speaker004:] Yeah, it's [disfmarker] it's not defined yet.
[speaker002:] And um you are probably also involved in that,
[speaker004:] Um [disfmarker] Yeah.
[speaker002:] right? uh together with the usual gang, um Petra and Jan
[speaker004:] Mmm. Yeah, there's a meeting next next week I think
[speaker002:] OK because That's [disfmarker] Those are the [disfmarker] I think the [disfmarker] the true key issues is how does the whatever comes out of the language input pipeline look like and then what the action planner does with it [disfmarker] and how that is uh specified. I didn't think of the internal working of the uh the action planner and the language [disfmarker] uh the function model as sort of relevant. Because what [disfmarker] what they take is sort of this [disfmarker] this fixed representation of a [disfmarker] of an intention. And that can be as detailed or as crude as you want it to be.
[speaker001:] Mm hmm.
[speaker002:] But um the internal workings of of the [disfmarker] whether you know there're dialogue [disfmarker] action planners that work with belief nets that are action planners that work with you know state automata. So that shouldn't really matter too much. I mean it does matter because it does have to keep track of you [disfmarker] we are on part six of r a route that consists of eight steps and so forth
[speaker006:] Yeah, th there [disfmarker] there [disfmarker] I think there are a lot of reasons why it matters.
[speaker001:] Right.
[speaker006:] OK, so that uh, for example, the i it's the action planner is going to take some spec and s make some suggestions about what the user should do. What the user says after that is going to be very much caught up with what the action planner told it.
[speaker001:] Yes.
[speaker006:] If the [disfmarker] If the parser and the language end doesn't know what the person's been told OK th it's you're making your life much more difficult than it has to be.
[speaker002:] Yeah.
[speaker006:] Right? So if someone says the best t to uh go there is by taxi, let's say. Now the planner comes out and says you wanna get there fast, take a taxi. OK. And the language end doesn't know that. OK, there's all sorts of dialogues that won't make any sense which would be just fine.
[speaker001:] hmm
[speaker006:] uh
[speaker002:] Yeah.
[speaker001:] That would b but that [disfmarker] I think that [disfmarker] that uh point has been realized and it's [disfmarker] it's not really um been defined yet but there's gonna be some kind of feedback and input from uh the action planner into all the analysis modules, telling them what to expect and what the current state of the discourse is.
[speaker004:] Mmm.
[speaker001:] Beyond what's currently being implemented which is just word lists.
[speaker006:] Yeah, but this is not the st this is not just the state of the discourse.
[speaker002:] Mm hmm.
[speaker001:] Of [disfmarker] of special interest.
[speaker006:] This is actually the state of the plan. That's why
[speaker002:] Mm hmm.
[speaker001:] Yes, Yes, Mm hmm yeah.
[speaker006:] OK so it [disfmarker] z and s uh, It's great if people are already taking that into account. But One would have t have to see [disfmarker] see the details.
[speaker001:] The specifics aren't really there yet. Yes.
[speaker006:] Yeah.
[speaker001:] So, there's work to do there.
[speaker006:] So anyway, Robert, that's why I was thinking that
[speaker002:] Mm hmm.
[speaker006:] um I think you're gonna need [disfmarker] We talked about this several times that [disfmarker] that [disfmarker] the [disfmarker] the input end is gonna need a fair amount of feedback from the planning end.
[speaker001:] hmm
[speaker006:] In [disfmarker] in one of these things which are [disfmarker] are much more continuous than the [disfmarker] just the dialogue over movies and stuff.
[speaker001:] Yeah.
[speaker004:] Mmm.
[speaker001:] And even on [disfmarker] on a more basic level the [disfmarker] the action planner actually needs to be able to have um an expressive power that can deal with these structures.
[speaker006:] Hmm?
[speaker001:] And not just um say um [disfmarker] um the dialogue um will consist of ten possible states and th these states really are fixed in [disfmarker] in a certain sense.
[speaker006:] Would there be any chance of getting the terminology changed so that the dialogue planner was called a "dialogue planner"?
[speaker001:] You have to [disfmarker]
[speaker006:] Because there's this other thing The o There's this other thing in [disfmarker] in the tourist domain which is gonna be a route planner
[speaker001:] That'd be nice.
[speaker006:] or [disfmarker] It's really gonna be an action planner. And [comment] i it [disfmarker]
[speaker001:] It oughta be called a [disfmarker] a dialogue manager. cuz that's what everybody else calls it.
[speaker006:] I would think, yeah.
[speaker004:] Mmm.
[speaker006:] Huh?
[speaker001:] Yeah.
[speaker006:] So, s So what would happen if we sent a note saying "Gee we've talked about this and couldn't we change this uh th the whole word?" I have no idea how complicated these things are.
[speaker002:] Probably close to impossible.
[speaker001:] Depends on who you talk to how. We'll see. I'll go check, cause I completely agree.
[speaker004:] Mmm.
[speaker001:] Yeah, and I think this is just for historical reasons within uh, the preparation phase of the project and not because somebody actually believes it ought to be action planner. So if there is resistance against changing it, that's just because "Oh, We don't want to change things." That [disfmarker] that not deep reason
[speaker006:] OK, anyway. I if [disfmarker] if that c in persists then we're gonna need another term. for the thing that actually does the planning of the uh routes and whatever we are doing for the tourist.
[speaker002:] That's external services.
[speaker006:] Yeah, but that's not g eh tha That ha has all the wrong connotations. it's [disfmarker] it sounds like it's you know stand alone. It doesn't interact, it doesn't That's why I'm saying. I think you can't [disfmarker] it's fine for looking up when T you know when the show's on TV. You go to th but I [disfmarker] I [disfmarker] I [disfmarker] I think it's really [disfmarker] really wrong headed for something that you [disfmarker] that has a lot of state, it's gonna interact co in a complicated way with the uh understanding parts.
[speaker002:] Yeah. Yeah I think just the [disfmarker] the spatial planner and the route planner I showed you once the interac action between them among them in the deep map system
[speaker006:] Right.
[speaker002:] so [disfmarker] a printout of the communication between those two fills up I don't know how many pages and that's just part of how do I get to one place.
[speaker001:] Hmm
[speaker002:] It's really insane. and uh but um so this is um definitely a good point to get uh Michael into the discussion. Or to enter his discussion, actually. That's the way around.
[speaker001:] Yeah, Marcus.
[speaker002:] Markus Is he new in the [disfmarker] in the?
[speaker001:] Wh where's? Yeah, he's [disfmarker] he started um I think January.
[speaker004:] Yeah.
[speaker001:] And he's gonna be responsible for the implementation of this action planner. Dialogue manager.
[speaker002:] Is he gonna continue with the old [disfmarker] uh [disfmarker] thing?
[speaker001:] No, no he's completely gonna rewrite everything. In Java.
[speaker002:] OK.
[speaker001:] OK so that's interesting.
[speaker002:] Yes I was just [disfmarker] that's my next question
[speaker001:] hmm
[speaker002:] whether we're [disfmarker] we're gonna stick to Prolog or not.
[speaker001:] No. No, that's gonna be phased out.
[speaker006:] Yeah.
[speaker002:] OK But I do think the [disfmarker] the function modeling concept has a certain [disfmarker] makes sense in a [disfmarker] in a certain light
[speaker001:] Yeah.
[speaker002:] because the action planner should not be [disfmarker] or the dialogue manager in that case should not um w have to worry about whether it's interfacing with um something that does route planning in this way or that way
[speaker001:] Mm hmm.
[speaker006:] I I totally agree. Sure.
[speaker002:] huh, it j
[speaker006:] Yeah I [disfmarker] I agree. There is [disfmarker] there's a logic to dialogue which [disfmarker] which is [disfmarker] is separable. I Yeah.
[speaker002:] and it [disfmarker] cant [disfmarker] sort of formulate its what it wants in a [disfmarker] in a rather a abstract uh way, you know f "Find me a good route for this."
[speaker006:] Mm hmm.
[speaker002:] It doesn't really have to worry ab how route planner A or how route planner B actually wants it. So this is [disfmarker] seemed like a good idea. In the beginning.
[speaker006:] It's tricky. It's tricky because one could well imagine [disfmarker] I think it will turn out to be the case that uh, this thing we're talking about, th the extended n uh knowledge modeler will fill in some parameters about what the person wants. One could well imagine that the next thing that's trying to fill out the detailed uh, route planning, let's say, will also have questions that it would like to ask the user. You could well imagine you get to a point where it's got a [disfmarker] a choice to make and it just doesn't know something. And so y you would like it t also be able to uh formulate a query.
[speaker001:] Mm hmm.
[speaker006:] And to run that back through uh. the dialogue manager and to the output module and back around.
[speaker002:] hmm
[speaker006:] And a I a a good design would [disfmarker] would allow that to happen.
[speaker002:] a lot of, yeah
[speaker004:] Mmm.
[speaker006:] If [disfmarker] if you know if [disfmarker] if you can't make it happen then you [disfmarker] you do your best.
[speaker001:] Yeah but that doesn't necessarily contradict um an architecture where there really is a pers a def well defined interface.
[speaker006:] I totally agree.
[speaker001:] and [disfmarker] and
[speaker006:] But [disfmarker] but what it nee but th what the point is the in that case the dialogue manager is sort of event driven. So the dialogue manager may think it's in a dialogue state of one sort, and this [disfmarker] one of these planning modules comes along and says "hey, right now we need to ask a question".
[speaker001:] Mm hmm.
[speaker006:] So that forces the dialogue manager to change state.
[speaker001:] Yes
[speaker006:] OK. It could be y
[speaker001:] Sure, ye yeah I [disfmarker] I think that's [disfmarker] that's the um concept that people have,
[speaker006:] Yeah, yeah it [disfmarker] it [disfmarker] OK.
[speaker001:] yep. And [disfmarker] and the [disfmarker] the underlying idea of course is that there is something like kernel modules with kernel functionality that you can plug uh certain applications like tourist information or um the home scenario with uh controlling a VCR and so on. And then extend it to an arbitrary number of applications eventually. So [disfmarker] wouldn't That's an additional reason to have this well defined interface
[speaker006:] Oh, yeah, yeah.
[speaker001:] and keep these things like uh tourist information external. And then call it external services.
[speaker002:] Hmm.
[speaker001:] But of course the [disfmarker] the more complex [disfmarker]
[speaker002:] Yeah, there is another philosophical issue that I think you know you can [disfmarker] evade
[speaker001:] yep.
[speaker002:] but, at at least it makes sense to me that sooner or later uh [disfmarker] a service is gonna come and describe itself to you. and that's sort of what Srini is working on in [disfmarker] in [disfmarker] in the DAML uh project where um you [disfmarker] you find a GIS about [disfmarker] that gives you information on Berkeley,
[speaker001:] Yeah.
[speaker002:] and it's [disfmarker] it's gonna be there and tell you what it can do and how it wants to do things. and so you can actually interface to such a system without ever having met it before and the function modeler and a self description of the um external service haggle it out
[speaker001:] Hmm.
[speaker002:] and you can use the same language core, understanding core to interface with planner A, planner B, planner C and so forth.
[speaker001:] Hmm.
[speaker004:] Mmm.
[speaker002:] Which is, you know, uh [disfmarker] uh [disfmarker] utopian [disfmarker] completely utopian at the moment, but slowly, you know, getting into the realm of the uh contingent.
[speaker001:] Hmm.
[speaker002:] But we are facing of course much more um realistic problems. And language input for example, is of course uh crucial you know also when you do the sort of deep understanding analysis that we envision. um Then of course, the uh um, you know what is it [disfmarker] poverty of the stimulus, yet the m uh the less we get of that the better. and um so we [disfmarker] we're thinking, for example how much syntactic analysis actually happens already in the parser.
[speaker004:] Hmm.
[speaker002:] and whether one could interface to that potentially
[speaker004:] Yeah, are there currently is uh no syntactic analysis but in the next release there will be some.
[speaker002:] Hmm.
[speaker006:] How's it [disfmarker]
[speaker004:] unless and it's um uh you can access this
[speaker006:] S so uh y we [disfmarker] we looked at the e current pattern matching thing.
[speaker004:] Hmm.
[speaker006:] And as you say it's just a surface pattern matcher. Uh, So what are [disfmarker] what are the plans roughly?
[speaker004:] um it's to [disfmarker] to integrate and syntactic analysis. and um add some more features like segmentation. So then an utter more than one utterance is [disfmarker] There um there's often uh pause between it and a segmentation occurs.
[speaker006:] So, the um [disfmarker]
[speaker004:] um
[speaker006:] So the idea is to uh [disfmarker] have a pa y y a particular [disfmarker]
[speaker004:] yeah
[speaker006:] Do you have a particular parser in mind? Is it uh [disfmarker] partic d I mean have you thought through [disfmarker]? Is it an HPSG parser? Is it a whatever?
[speaker004:] No [disfmarker] no it's [disfmarker] uh I think it's it's totally complicated for it's just one [disfmarker] one person
[speaker006:] OK.
[speaker004:] and so I have to keep the [disfmarker]
[speaker006:] Oh, you have to do it. You have to do it, yeah.
[speaker004:] Yeah, ah and so [vocalsound] things must be simpler
[speaker006:] I see, so
[speaker004:] but uh, Miel syntactic analysis with um finite state transducers.
[speaker006:] But the people at D F Yeah. People at DFKI have written a fair number of parsers. Other [disfmarker] you know, people over the years. uh have written various parsers at DFKI. None of them are suitable? I [disfmarker] I [disfmarker] I d I'm asking. I don't know.
[speaker004:] Yeah, uh the problem is th that it has to be very fast because um if you want to for more than one path anywhere
[speaker006:] OK.
[speaker004:] what's in the latches from the speech recognizer
[speaker006:] Mm hmm.
[speaker004:] so it's speed is crucial. uh And they are not fast enough.
[speaker006:] Mm hmm.
[speaker004:] And they also have to be very robust. cuz of um speech recognition errors and
[speaker006:] OK. So, um [disfmarker] So there was a chunk parser in Verbmobil, that was one of the uh branchers. You know they [disfmarker] d th I c There were these various uh, competing uh syntax modules. And I know one of them was a chunk parser and I don't remember [pause] who did that.
[speaker004:] I think it's that
[speaker002:] A Alan?
[speaker004:] might, at Tuebingen I thought.
[speaker006:] Yeah I d I don't remember.
[speaker004:] was [disfmarker] Do you know something about that?
[speaker001:] Tubingen was at least involved in putting the chunks together
[speaker004:] In Tub at [disfmarker]
[speaker001:] I [disfmarker] can't quite recall whether they actually produced the chunks in the first place.
[speaker004:] oh
[speaker006:] Uh. I see. Yeah, that's right.
[speaker001:] Or wh
[speaker006:] There w
[speaker004:] Oh from [disfmarker] from Stuttgart,
[speaker006:] That's right. They w They had [disfmarker] There were [disfmarker] This was done with a two phase thing, where [comment] the chunk parser itself was pretty stupid
[speaker004:] yeah, also
[speaker006:] and then there was a kind of trying to fit them together that h used more context.
[speaker001:] Right. Yeah
[speaker006:] Right?
[speaker001:] Well you s and [disfmarker] and especially you did some [disfmarker] some um, l um was a learning based approach which learned from a big corpus of [disfmarker] of trees.
[speaker006:] Right.
[speaker004:] Mm hmm.
[speaker006:] Right.
[speaker001:] And yes the [disfmarker] it [disfmarker] the chunk parser was a finite state machine that um Mark Light originally w worked on in [disfmarker] while he was in Tuebingen and then somebody else in Tuebingen picked that up. So it was done in Tuebingen, yeah. Definitely.
[speaker006:] But is that the kind of thing y It sounds like the kind of thing that you were thinking of.
[speaker004:] yeah.
[speaker001:] Yeah I guess it's similar.
[speaker004:] yeah that's In this direction, yes
[speaker006:] What?
[speaker004:] Yeah, it's in [disfmarker] in this direction.
[speaker006:] Hmm.
[speaker002:] The [disfmarker] From Michael Strube, I've heard very good stuff about the chunk parser that is done by FORWISS, uh, which is in embassy doing the parsing.
[speaker001:] Mm hmm.
[speaker002:] So this is sort of [disfmarker] came as a surprise to me that you know, embassy s [comment] is featuring a nice parser but it's [pause] what I hear. One could also look at that and see whether there is some synergy possible.
[speaker004:] Mm hmm, yeah, it would be very interesting, Mm hmm. Mmm, yeah.
[speaker002:] And they're doing chunk parsing and it's uh [disfmarker] I [disfmarker] I can give you the names of the people who do it there. But um. Then there is of course more ways of parsing things.
[speaker006:] Of course. But [disfmarker] But uh given th the constraints, that you want it to be small and fast and so forth, my guess is you're probably into some kind of chunk parsing. And uh I'm not a big believer in this um statistical you know, cleaning up uh It [disfmarker] That seems to me kind of a last resort if uh you can't do it any other way. uh but I dunno. It may [disfmarker] i i may be that's what you guys finally decide do.
[speaker004:] Hmm.
[speaker006:] Uh. And have you looked [disfmarker] uh just [disfmarker] again for context [disfmarker]
[speaker004:] Mm hmm.
[speaker006:] There is this [disfmarker] this one that they did at SRI some years ago [disfmarker] Fastus?
[speaker004:] um
[speaker006:] a [disfmarker]
[speaker004:] yeah, I've [disfmarker] I've looked at it but [disfmarker] but it's no [disfmarker] not much uh information available.
[speaker006:] ah!
[speaker004:] I found, but it's also finite state transducers, I thought.
[speaker006:] It is. Yeah. I mean [disfmarker] it's [disfmarker] it was pretty ambitious.
[speaker004:] and
[speaker006:] And of course it was English oriented, um w
[speaker004:] Yeah, and [disfmarker] and Purely finite state transducers are not so good for German since there's um
[speaker006:] Right. Yeah, I guess that's the point is [disfmarker] is all the morphology and stuff.
[speaker004:] The word order is [disfmarker] is uh not fixed
[speaker006:] And English is all th all word order. And it makes a lot more sense.
[speaker004:] Yeah.
[speaker006:] And [disfmarker] e Yeah, OK. Good point. So in [disfmarker] in [disfmarker] in German you've got uh most of this done with
[speaker004:] Mm hmm. Also it's uh [disfmarker] it's um [disfmarker] Yes, uh the um choice between uh this processing and that processing and my template matcher.
[speaker006:] Right. Right. So what about Um Did y like Morfix? a a e y you've got stemmers? Or is that something that [disfmarker]
[speaker004:] Um, yeah but it's all in the [disfmarker] in the lexicon.
[speaker006:] But did you have that?
[speaker004:] So it's [disfmarker] Yeah th the information is available.
[speaker006:] OK. I see. So, but [disfmarker] So y you just connect to the lexicon
[speaker004:] So [disfmarker] Yeah
[speaker006:] and uh at least for German you have all [disfmarker] all of the [disfmarker] uh the stemming information.
[speaker004:] Yeah, we can, oh yeah. We have knowledge bases from [disfmarker] from Verbmobil system we can use
[speaker006:] Yep.
[speaker004:] and so.
[speaker006:] Right. But it [disfmarker] it [disfmarker] it doesn't look like i you're using it. I didn't n see it being used in the current template uh parser. I [disfmarker] I didn't see any Uh [disfmarker] of course we l actually only looked at the English.
[speaker004:] It [disfmarker]
[speaker006:] Did we look at the German?
[speaker004:] um
[speaker006:] I don't remember. So w wha
[speaker004:] Yeah, but [disfmarker] but it's used for [disfmarker] for stem forms.
[speaker001:] n Well I think [disfmarker] I think there's some misunderstanding here
[speaker006:] i
[speaker004:] Oh, OK.
[speaker001:] it's [disfmarker] Morphix is not used on line. s so the lexicon might be derived by Morphix
[speaker004:] What?
[speaker001:] but What [disfmarker] what's happening on line is just um um a [disfmarker] a retrieval from the lexicon which would give all the stemming information
[speaker006:] Right. Right.
[speaker004:] Hmm.
[speaker001:] so it would be a full foreign lexicon.
[speaker006:] And that's what you have.
[speaker004:] Yeah
[speaker001:] Yep.
[speaker006:] OK. What [disfmarker] uh I didn't reme
[speaker002:] We threw out all the forms.
[speaker006:] Huh?
[speaker002:] We threw out all the forms because, you know, English, well [disfmarker]
[speaker006:] Oh OK, so it [disfmarker] yeah, s s I thought I'd [disfmarker]
[speaker004:] Mm hmm.
[speaker006:] So in German then you actually do case matching and things like in the [disfmarker] in the pattern matcher or not?
[speaker004:] um Not yet but it's planned to do that.
[speaker006:] OK. Cuz I r I didn't reme I didn't think I saw it. Have we looked at the German?
[speaker004:] Yeah
[speaker006:] Oh, I haven yeah that's [disfmarker] getting it from the lexicon is just fine. Yeah, yeah, yeah.
[speaker001:] Sure,
[speaker004:] Oh yes.
[speaker001:] right.
[speaker006:] No problem with that. um Yeah and here's the case where the English and the German might really be significantly different. In terms of if you're trying to build some fast parser and so forth and [disfmarker] You really might wanna do it in a significantly different way. I don't know. So you've [disfmarker] you guys have looked at this? also? in terms of You know, w if you're doing this for English as well as German Um Do you think now that it would be this [disfmarker] doing it similarly?
[speaker004:] um Yeah, it's um I think it's um yes, it's [disfmarker] it's um possible to [disfmarker] to do list processing. and Maybe this is um more adequate for English and in German um set processing is used.
[speaker006:] Set.
[speaker004:] Maybe yeah. Some extensions uh have to be made. For [disfmarker] for a English version
[speaker006:] Mmm. OK. Interesting. Not easy.
[speaker002:] Well there's m I'm sure there's gonna be more discussion on that after your talk.
[speaker004:] Mm hmm,
[speaker006:] Right.
[speaker004:] yeah.
[speaker002:] We're just gonna foreshadow what we saw that
[speaker006:] Right.
[speaker002:] and um
[speaker006:] Now actually, um Are you guys free at five? Or [disfmarker] Do you have to go somewhere at five o'lock tonight? W in ten minutes?
[speaker004:] Ah [disfmarker] mmm. No.
[speaker001:] uh [disfmarker] uh [disfmarker] I think we're expect [disfmarker]
[speaker004:] Oder there was an [disfmarker] talk?
[speaker001:] Yeah, there [disfmarker] there's the um practice talk.
[speaker004:] uh Mmm, yeah.
[speaker006:] Great. So you're going to that.
[speaker001:] Yeah, that [disfmarker] that's what we were planning to do.
[speaker006:] That's good, because that will uh tell you a fair amount about The form of semantic construction grammar that we're using.
[speaker001:] Yeah.
[speaker006:] so [disfmarker] So I th I think that probably as good an introduction as you'll get.
[speaker001:] Mm hmm.
[speaker004:] Ah.
[speaker006:] Uh to the form of [disfmarker] of uh [disfmarker] conceptual grammar that [disfmarker] that w we have in mind for this.
[speaker004:] Mmm, ah.
[speaker006:] It won't talk particularly about how that relates to what uh Robert was saying at the beginning. But let me give you a very short version of this. So we talked about the fact that There're going to be a certain number of decisions That you want the knowledge modeler to make, that will be then fed to the function module, that does uh, route planning. It's called the "route planner" or something.
[speaker001:] Mm hmm.
[speaker006:] So there are these decisions. And then one half of this we talked about at little bit is how if you had the right information, if you knew something about what was said and about th the something about was the agent a tourist or a native or a business person or uh young or old, whatever. That information, and also about the Uh, what we're calling "the entity", Is it a castle, is it a bank? Is it a s town square, is it a statue? Whatever. So all that kind of information could be combined into decision networks and give you decisions. But the other half of the problem is How would you get that kind of information from the parsed input? So, um So what you might try to do is just build more templates, saying uh we're trying to build a templ you know build a template that w uh somehow would capture the fact that he wants to take a picture.
[speaker004:] Mmm.
[speaker006:] OK? And [disfmarker] and we could [disfmarker] you could do this. And it's a small enough domain that probably you, you know [disfmarker]
[speaker004:] Mmm.
[speaker006:] OK. You could do this. But uh from our point of view this is also a research project and there are a couple of people not here for various reasons who are doing doctoral dissertations on this,
[speaker001:] Mm hmm.
[speaker006:] and the idea that we're really after is a very deep semantics based on cognitive linguistics and the notion that there are a relatively small number of primitive conceptual schemas that characterize a lot of activity. So a typical one in this formulation is a container. So this is a static thing. And the notion is that all sorts of physical situations are characterized in terms of containers. Going in and out the portals and con
[speaker004:] Mmm.
[speaker006:] OK. But also, importantly for Lakoff and these guys is all sorts of metaphorical things are also characterized this way. You get in trouble and you know et cetera
[speaker004:] Mmm.
[speaker006:] and so [disfmarker] s So, what we're really trying to do is to map from the discourse to the conceptual semantics level. And from there to the appropriate decisions. So another one of these primitive, what are called "image schemas", is uh goal seeking.
[speaker001:] Mm hmm.
[speaker006:] So this a notion of a source, path, goal, trajector, possibly obstacles.
[speaker001:] Mm hmm.
[speaker006:] And the idea is this is another conceptual primitive. And that all sorts of things, particularly in the tourist domain, can be represented in terms of uh source, path and goal.
[speaker001:] Mm hmm.
[speaker006:] So the idea would be could we build an analyser that would take an utterance and say "Aha! th this utterance is talking about an attempt to reach a goal. The goal is this, the pers the, uh traveller is that, uh the sor w where we are at now is is this, they've mentioned possible obstacles, et cetera." So th the [disfmarker] and this is an [disfmarker] again attempt to get very wide coverage. So if you can do this, then the notion would be that across a very large range of domains, you could use this deep conceptual basis as the interface.
[speaker001:] Mm hmm. Mm hmm.
[speaker006:] And then, uh The processing of that, both on the input end, recognizing that certain words in a language talk about containers or goals, et cetera, and on the output end, given this kind of information, you can then uh make decisions about what actions to take. Provides, they claim, a very powerful, general notion of deep semantics. So that's what we're really doing.
[speaker001:] Mm hmm.
[speaker006:] And Nancy is going to [disfmarker] Her talk is going to be not about using this in applications, but about modeling how children might learn this kind of uh deep semantic grammar.
[speaker001:] Mm hmm. Yep, yep. And how do you envision um the [disfmarker] the um this deep semantic to be worked with. Would it be highly ambiguous if and then there would be another module that takes that um highly underspecified deep semantic construction and map it onto the current context to find out what the person really was talking about in that context.
[speaker006:] Well that's [disfmarker] that's [disfmarker] that's where the belief net comes in.
[speaker001:] or [disfmarker] or a [disfmarker]
[speaker006:] So th the idea is, let's take this business about going to the Powder Tower.
[speaker001:] Mm hmm.
[speaker006:] So part of what you'll get out of this will be the fact tha w if it works right, OK, that this is an agent that wants to go to this place and that's their goal and there will be additional situational information.
[speaker001:] Mm hmm. Oh, OK.
[speaker006:] Uh, OK,
[speaker001:] th
[speaker006:] part of it comes from the ontology. The tower is this kind of object.
[speaker001:] Mm hmm. Yeah, OK.
[speaker006:] Part of it comes from the user model.
[speaker001:] Mm hmm.
[speaker006:] And the idea of the belief net is it combines the information from the dialogue which comes across in this general way,
[speaker001:] Mm hmm.
[speaker006:] you know this is a [disfmarker] this is a goal seeking behavior, along with specific information from the ontology about the kinds of objects involved
[speaker001:] Yeah OK, Yeah, yep yep yep yep
[speaker006:] and about the situation about "Is it raining?" I don't know. Whatever it is. And so that's the belief net that we've laid out.
[speaker001:] Mm hmm.
[speaker006:] And so th the coupling to the situation comes in this model from, at th at th at the belief net, combining evidence from the dialogue with the ontology with the situation.
[speaker001:] Yeah.
[speaker004:] Hmm.
[speaker006:] But Nancy isn't gonna talk about that,
[speaker001:] Yeah,
[speaker006:] just about the um
[speaker001:] oh yeah, I see, yeah yeah, really.
[speaker002:] First steps.
[speaker006:] Right. The [disfmarker] the construction grammar.
[speaker002:] And she's gonna start in a minute.
[speaker006:] In a minute.
[speaker004:] Ah, OK.
[speaker006:] OK.
[speaker007:] Is it i in, then, your place, in five [disfmarker] five A?
[speaker001:] Alright.