December 3, 2019

567 words 3 mins read

How knowledge graphs can help dramatically improve recommendations

How knowledge graphs can help dramatically improve recommendations

Collaborative filtering is great for recommendations, yet it suffers from the cold-start problem. New content with no views is ignored, and new users get poor recommendation. Aurlien Gron shares a solution: knowledge graphs. With a knowledge graph, you can truly understand your users' interests and make better, more relevant recommendations.

Talk Title How knowledge graphs can help dramatically improve recommendations
Speakers Aurélien Géron (Kiwisoft)
Conference Strata Data Conference
Conf Tag Making Data Work
Location London, United Kingdom
Date May 23-25, 2017
URL Talk Page
Slides Talk Slides
Video

Good recommendations turn occasional users into daily users. When users don’t have to search for good content, they engage more. Collaborative filtering is one of the most successful tools for recommending the right content to the right audience, yet it requires plenty of signal to work efficiently. New users with little history get completely unpersonalized recommendations, and fresh content gets recommended to no one (or worse, to the wrong audience). This is known as the cold-start problem. So what’s the solution? If a brand-new user watches a freshly uploaded biking video, you would probably want to recommend more biking content, and possibly suggest related topics such as fitness. In short, instead of direct content-to-content recommendations, you would go for content-to-topic-to-content. The first step is to build a system that automatically figures out what your content is about. One option would be to just parse the text (i.e., the video title and description) and extract unusually frequent tuples of words (using tf–idf). However, plain text can be ambiguous (does “football” refer to American football or to soccer?), and it can be redundant (“sky diving” is the same as “parachuting”) and messy (“Mikael Jackson” is clearly “Michael Jackson” misspelled). Aurélien Géron shares a much better option: leveraging the power of knowledge graphs such as Wikidata, DBpedia, and Google’s KG (initially based on Freebase, which has been sunsetted in favor of Wikidata). Each node in a graph represents a unique, unambiguous topic, and these topics are connected into a gigantic machine-queryable graph. This structure can be exploited to provide meaningful, consistent, browsable, and personalized content (e.g., list the most famous professional soccer players born in the user’s city). Many signals can be used to identify a content’s topic, from text (title, description, comments, anchors, search queries, etc.) to user behavior (e.g., topics explored during the same session) to audiovisual content analysis (using deep learning), and beyond. No tool is perfect, and knowledge graphs are no exception. In particular, although they are great at making good recommendations for new users and serving fresh content to the right audience, they are not ideal for new topics since it takes time for a new topic to be added to a knowledge graph. One solution is to use a mixed vocabulary including both KG topics and plain text. Beyond recommendations, better understanding what your content is actually about can help you drive your content strategy (e.g., do users engage with cooking videos?), enable context-aware ad targeting (e.g., display a makeup ad on beauty tips content), improve search (e.g., people searching for “Paris” could get only results about the city, plus a disambiguation box asking them whether they meant “Paris Hilton”, or the band “Paris”), structure the user experience (e.g., if the content is about a movie, show the main actor bios), help detect spam (e.g., why is the content unrelated to its title?), and much more.

comments powered by Disqus