You also get :
We met a new person last night but he really showed up my friends.
Which means he made my friends feel bad about themselves or something like that.
Or :
This guy at work really showed me up today...
Meaning much the same thing...picking out one's bad points and so on...trying to make one look bad...
Oh my God. Ok, I am a human being, and that makes no sense to me and I wouldn't think in a million years that that was what that meant !!!!
Not living in your part of the world of course is the reason.
My bot will not recognize those semantics.. it, like me, will simply report that it doesn't understand those statements.
This brings up, "Locality" in semantics. When my bot goes online, sorry guys, but you will have to add those locality-specific semantics to the system yourselves lol
Actually, later I will have the system learn semantics by conversation.
** there seems to be no "global" semantics that fits in all cases **
Perhaps a certain percentage, like 80 or 90 % hopefully, of semantics is common throughout the English speaking world, and 10 to 20% are semantics that only apply to certain parts of the world.
No bot can be blamed for not understanding, universally, all areas, and their semantics, "out of the box" ... . .no human does.
* a related concept ... and I'm not sure if it only applies to Canada... but we have this thing, "ay"... where we say "You're going to the party, ay?" which means "You're going to the party, *right*??" It literally means "is this correct? or "do you agree"?" with the sentence right before the "ay". By the way, if you heard about the "eh" in Canada.... "ay" and "eh" are different. "eh" in Canada is a French Canadian pronunciation problem (french can't say the English "th".. so they pronounce "that" as "dat") I'm not French.. Polish/German descent. But "eh" and "ay" are quite different.
I'm interested though -- how much work are all of you going to put into accommodating "expressions" for every area of the world? My bot will support 'ay' , but not 'eh'. It's a Canadian bot after all
Art -- your point is well taken regarding the unnecessary prepositions trailing sentences. Bots will have to do MUCH work in permutations for this. They will have to make a first attempt at parsing, oh, bad parse? ok, let's try removing this word, ok, try again, nope, try adding this word, try again, ok. . now the parse makes sense.
It will just add a LOT of unnecessary CPU cycles, and longer wait time to respond, by the fact that it has to do all this extra work.
the bot has to --
a) find misspelled words... generate all possible "closest" matches.. try each one
b) determine if there are any unnecessary words, try removing each one (or some combination of), try again
c) determine if there are words that *should* have been there, but were not (sometimes laziness causing people to remove 'to' for example in "I want create a chatbot".. missing 'to'.... changes the meaning.
so, there will be one thing to having a bot that can carry a conversation intelligently, assuming half decent input, and another problem altogether to make it handle varying degrees of human laziness.... that last one is going to require immense processing time if the input is VERY BAD.