Apostrophe in custom word prevents matching

I’m developing a custom lexicon of plant names, which include “Queen Anne’s lace” and “baby’s breath”, however when a word in my custom lexicon includes an apostrophe, it doesn’t seem to match. Is there something I need to do to force it to use the custom lexicon?

Additionally, I was looking through compromise’s default lexicon and it seems like words in there with apostrophes aren’t matching, either:

nlp("Starbucks is a great restaurant.").match("#Organization").out("array") // ✅ nlp("Applebee's is a great restaurant.").match("#Organization").out("array") // ❌ https://github.com/spencermountain/compromise/blob/52fb03e7a26e8caed08bf04d893b0044aab4c538/data/lexicon/nouns/organizations.js#L275

[spencermountain]

hey @msjonker this is tagging now in 14.4.0 it just throws-away the apostrophe, when creating the lexicon. if you want to ensure it’s a Possessive, you can do something like:

doc.match('queen (anne && #Possessive) lace').tag('Flower')

cheers

[msjonker]

Sorry, for the late reply; I was on vacation last week.

This solution looks great! I was working on a PR that evaluated matching the normal form of the term first, then falling back to the machine form of the term, but this seems like a much better solution.

Thanks!