Yeah. My mistake in explanation. But it really does help with better relevance 
in the returned documents

> On Oct 25, 2019, at 12:39 PM, Audrey Lorberfeld - audrey.lorberf...@ibm.com 
> <audrey.lorberf...@ibm.com> wrote:
> 
> Oh I see I see 
> 
> -- 
> Audrey Lorberfeld
> Data Scientist, w3 Search
> IBM
> audrey.lorberf...@ibm.com
> 
> 
> On 10/25/19, 12:21 PM, "David Hastings" <hastings.recurs...@gmail.com> wrote:
> 
>    oh i see what you mean, sorry, i explained it incorrectly.
>     those sentences are what would be in the index, and a general search for
>    'rush limbaugh' would come back with results where he is an entity higher
>    than if it was two words in a sentence
> 
>    On Fri, Oct 25, 2019 at 12:12 PM David Hastings <
>    hastings.recurs...@gmail.com> wrote:
> 
>> nope, i boost the fields already tagged at query time against teh query
>> 
>> On Fri, Oct 25, 2019 at 12:11 PM Audrey Lorberfeld -
>> audrey.lorberf...@ibm.com <audrey.lorberf...@ibm.com> wrote:
>> 
>>> So then you do run your POS tagger at query-time, Dave?
>>> 
>>> --
>>> Audrey Lorberfeld
>>> Data Scientist, w3 Search
>>> IBM
>>> audrey.lorberf...@ibm.com
>>> 
>>> 
>>> On 10/25/19, 12:06 PM, "David Hastings" <hastings.recurs...@gmail.com>
>>> wrote:
>>> 
>>>    I use them for query boosting, so if someone searches for:
>>> 
>>>    i dont want to rush limbaugh out the door
>>>    vs
>>>    i talked to rush limbaugh through the door
>>> 
>>>    my documents where 'rush limbaugh' is a known entity (noun) and a
>>> person
>>>    (look at the sentence, its obviously a person and the nlp finds that)
>>> have
>>>    'rush limbaugh' stored in a field, which is boosted on queries.  this
>>> makes
>>>    sure results from the second query with him as a person will be
>>> boosted
>>>    above those from the first query
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>>    On Fri, Oct 25, 2019 at 11:57 AM Nicolas Paris <
>>> nicolas.pa...@riseup.net>
>>>    wrote:
>>> 
>>>> Also we are using stanford POS tagger for french. The processing
>>> time is
>>>> mitigated by the spark-corenlp package which distribute the process
>>> over
>>>> multiple node.
>>>> 
>>>> Also I am interesting in the way you use POS information within solr
>>>> queries, or solr fields.
>>>> 
>>>> Thanks,
>>>>> On Fri, Oct 25, 2019 at 10:42:43AM -0400, David Hastings wrote:
>>>>> ah, yeah its not the fastest but it proved to be the best for my
>>>> purposes,
>>>>> I use it to pre-process data before indexing, to apply more
>>> metadata to
>>>> the
>>>>> documents in a separate field(s)
>>>>> 
>>>>> On Fri, Oct 25, 2019 at 10:40 AM Audrey Lorberfeld -
>>>>> audrey.lorberf...@ibm.com <audrey.lorberf...@ibm.com> wrote:
>>>>> 
>>>>>> No, I meant for part-of-speech tagging __ But that's
>>> interesting that
>>>> you
>>>>>> use StanfordNLP. I've read that it's very slow, so we are
>>> concerned
>>>> that it
>>>>>> might not work for us at query-time. Do you use it at
>>> query-time, or
>>>> just
>>>>>> index-time?
>>>>>> 
>>>>>> --
>>>>>> Audrey Lorberfeld
>>>>>> Data Scientist, w3 Search
>>>>>> IBM
>>>>>> audrey.lorberf...@ibm.com
>>>>>> 
>>>>>> 
>>>>>> On 10/25/19, 10:30 AM, "David Hastings" <
>>> hastings.recurs...@gmail.com
>>>>> 
>>>>>> wrote:
>>>>>> 
>>>>>>    Do you mean for entity extraction?
>>>>>>    I make a LOT of use from the stanford nlp project, and get
>>> out the
>>>>>> entities
>>>>>>    and use them for different purposes in solr
>>>>>>    -Dave
>>>>>> 
>>>>>>    On Fri, Oct 25, 2019 at 10:16 AM Audrey Lorberfeld -
>>>>>>    audrey.lorberf...@ibm.com <audrey.lorberf...@ibm.com>
>>> wrote:
>>>>>> 
>>>>>>> Hi All,
>>>>>>> 
>>>>>>> Does anyone use a POS tagger with their Solr instance
>>> other than
>>>>>>> OpenNLP’s? We are considering OpenNLP, SpaCy, and Watson.
>>>>>>> 
>>>>>>> Thanks!
>>>>>>> 
>>>>>>> --
>>>>>>> Audrey Lorberfeld
>>>>>>> Data Scientist, w3 Search
>>>>>>> IBM
>>>>>>> audrey.lorberf...@ibm.com
>>>>>>> 
>>>>>>> 
>>>>>> 
>>>>>> 
>>>>>> 
>>>> 
>>>> --
>>>> nicolas
>>>> 
>>> 
>>> 
>>> 
> 
> 

Reply via email to