Case in queries

[timfu]

"houses in summertown" fails for me, as does "houses in headington" etc.

I think it's about capitalization, as

"houses in Summertown" works as does "houses in Headington"

etc.

I guess we can live with this, but it would be great if we could just accept lowercase locations as well.

[LorenzBuehmann]

Yes, that's indeed a problem, but currently I see no solution to this problem. We use a POS tagger (e.g. http://nlp.stanford.edu:8080/parser/index.jsp) when processing the question.

houses in Summertown -> houses/NNS in/IN Summertown/NNP houses in Summertown -> houses/NNS in/IN Summertown/NN

Based on the POS tagging we decide whether it is a class or resource.

[timfu]

Could you add something to the error message, like if it's "in" followed by a lower-case, we add something like "try in upper case" or "did you mean...".

Doesn't have high priority, but I fear most people will run into this.