-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
“carpool from Lyon to Paris on December 31” #72
Comments
I think it is one of the best possible forms with our current datamodel: the intersection of carpools related to Lyon, Paris and December 31. |
I think we can do slightly better. If we consider that '?' has to be the |(?, instance of, carpool) ∩ (?, from, Paris) ∩ (?, to, Lyon)||∩ (?, With this expression, '?' is totally determined. We know that we are Tha datamodel is powerful! It's not dead!Glory! Le 27/12/2014 15:32, Tom Cornebize a écrit :
Marc Chevalier ENS de Lyon |
What is this pipe notation? |
I don't know where these pipes come from. I don't know if I have to thank Thunderbird or Markdown in Github. |
Just ignore them, they are useless. |
I was going to write the exact same answer as @s-i-newton . So strong +1 to his answer |
If the carpool module's programmer knows that he has to handle "on" for the day of the trip, I think it is not a problem. |
“on” is ambiguous and highly language-dependant (what would you do if On 27/12/2014 17:49, Tom Cornebize wrote:
|
Yes, it is. But the context (istance of carpool) determine the meaning. Thus, the module can give the meaning according with its utility. |
It depends of the context (e.g. "Who walked on the Moon?"). We could use the NER tag (the stuff between the brackets) to choose the predicate for a Shortly: what you are asking is possible.
"for" and "to" are also language-dependant. Moreover, we agreed that the translation work had to be done by the backend modules (this is what is doing Wikidata). |
http://askplatyp.us/?lang=en&q=carpool+from+Lyon+to+Paris+on+December+31
I'm not sure if there is a way to encode this in the datamodel, though.
The text was updated successfully, but these errors were encountered: