Right.
then y you 'd simply write , uh , these into  onto your  your white piece of paper. And you will get a lot of notes and stuff out of there. You won't get  you won't really get any C P T 's , therefore we need everything that  that configures to what the situation is , IE , the context dependent stuff. So you get whatever comes from discourse but also filtered. Uh , so only the ontology relevant stuff from the discourse plus the situation and the user model.
Mm - hmm.
And that fills in your CPT 's with which you can then query , um , the  the net that you just wrote and find out how thing X is construed as an utterance U. And the embedded JavaBayes works exactly like that , that once you  we have , you know , precise format in which to write it , so we write it down. You query it. You get the result , and you throw it away. And the  the nice thing about this idea is that you don't ever have to sit down and think about it or write about it. You may have some general rules as to how things can be  can be construed as what , so that will allow you to craft the  the  the initial notes. But it 's  in that respect it 's completely scalable. Because it doesn't have any prior , um , configuration. It 's just you need an ontology of the domain and you need the context dependent modules. And if this can be made to work at all ,  that 'd be kind of funky.