Live data from Hacker News

Shirt Without Stripes

github.com

141–150 of 639 posts

Re: Shirt Without Stripes

#141

I wonder why this problem hasn't been resolved yet, considering we had NLP systems capable of this for a decade now. Maybe it's too hard to scale to production. Or Pagerank is still better most of the time. Or plain old monopoly and risk aversion.

My bet is that sites are generally optimized to a keyword search and this kind NLP search engine would return subpar answers most cases.

Re: Shirt Without Stripes

#143
post #13

The point of this isn't asking how to apply boolean search operators, it's showing that the largest AI-focused companies in the world absolutely suck at NLP.

Why would you really apply NLP to a search engine though? Generally speaking a weighted keyword search is good enough 95% of the time and requires significantly less resources to perform.

Depends on your audience, but I imagine many find the answer boxes on Google search pretty useful. Getting the population of a city without having to click any links is probably good for your perceived value. For this you need some NLP tech to extract intent from the query and match it to the right entity in their knowledge graph (in addition to something to help you build the graph in the first place).

Google have a blog post from October last year with some more complex examples of where more sophisticated NLP helps https://www.blog.google/products/search/search-language-unde...

Re: Shirt Without Stripes

#144
post #13

The point of this isn't asking how to apply boolean search operators, it's showing that the largest AI-focused companies in the world absolutely suck at NLP.

Why would you really apply NLP to a search engine though? Generally speaking a weighted keyword search is good enough 95% of the time and requires significantly less resources to perform.

Because you want to sell shirts without stripes to customers who want them.

Re: Shirt Without Stripes

#145

I have noticed in the past few years google results have become noticeable worse for similar reasons. Google used to _surprise_ me with how good it was able to understand what I was really looking for even when I put in vague terms. I remember being shocked on several occasions when putting in half remembered sentences, lyrics, expressions from something I had heard years ago and it being the first! result. I almost…

That was when people built websites to deliver content. Now people build websites to get highly ranked in Google. No matter how good google's algos are, they can't win when the underlying content is just SEO'd garbage.

Re: Shirt Without Stripes

#147

I would never search for something this way. If I wanted to find a 4WD car, I wouldn't search for "cars without 2WD." Likewise, here, I would search for solid-colored shirts. And these services are limited to the content/terminology utilized by the cataloged sites/products. If I am selling a "black shirt" or a "solid black shirt," it is not google's job to catalog it as a "shirt without stripes," unless I advertise i…

Your car example makes sense because there are pretty much only 2 options. Unfortunately people don't search for "solid shirts". At best they search for "plain shirts", but there's a lot of taste to clothing that means people often do want a shirt without stripes, but are open to patterned/plain. I think searching "shirts without stripes" is very legitimate in fashion. I say this having built a clothing search functi…

So the one you built will exclude shirts with stripes if "shirts without stripes" is typed directly into a search box? Or there are secondary filters to omit and/or only show certain patterns?

Re: Shirt Without Stripes

#148

Earlier quoted context omitted.

I'd go as far as saying "AI" is only as good as someone has taken the time to program the use case.

So, it's really just a series of if statements?

One of the primary methods to join multiple learned models is a decision tree (or combination of decision trees making a decision forest), which can be simplified as a series of if statements/conditionals. So if you join a 'is it a shirt' model with a 'is it striped' model you get two sets of things, and with how big data approaches this it is something you can do quickly. As other people have pointed out the issue here is that the NLP of the actual search is not creating a negation of two sets, it is returning the intersect of sets 'is it a shirt', 'is it striped' and shrugging its shoulders and either intersecting it with 'things with the text without', or throwing up its hands entirely based on the context because it wasn't programmed to do something smarter.

Re: Shirt Without Stripes

#149

https://www.google.com/search?q=plain+shirt https://www.amazon.com/s?k=plain+shirt on edit: https://www.google.com/search?q=shirt+-stripes

The author doesn't want a plain shirt. He wants one without stripes. This includes harlequin shirts, shirts with logos, shirts with pictures, tie die shirts. All good, as long as they don't have stripes.

Re: Shirt Without Stripes

#150
post #13

The point of this isn't asking how to apply boolean search operators, it's showing that the largest AI-focused companies in the world absolutely suck at NLP.

Why would you really apply NLP to a search engine though? Generally speaking a weighted keyword search is good enough 95% of the time and requires significantly less resources to perform.

From a product perspective, I would say there is a reasonable expectation that a customer will provide that query and expect the results to come back with plain shirts. Anything different is a degraded customer experience. Sure, a technical user will understand which queries to provide better, but 90% of customers won't have that skillset. Its our job as engineers to serve those people, and the queries they provide.

So NLP is totally a thing you want to have in search. Arguably, its the whole point of search as it exists now.

Post reply on HN