When using the omnibox with extremely short query strings, the results are often very poor matches - this has been the behavior for a long time. However, Rich Entities makes these poor matches much more visible than they were before, which draws my eye to how bad they are. A couple of examples are attached.

In the completions for "z", the "Jay-Z" rich entity is the only match which isn't either a history match or a search suggestion. Both of the history matches are basically spurious, as are the search suggestions. The Jay-Z match stands out much more, though, and it drew me to notice how not-related to my query it is.

In the completions for "yah", all the other matches are related to "yahoo" - which makes good sense in the context of my navigation and search history. In the middle there's a large and bright match for a song I've never heard by an artist I've never listened to. It's weird to sort of visually promote what is by far the least relevant match in this set.
 

Deleted: Screen Shot 2018-07-11 at 1.23.26 PM.png 88.1 KB

	Screen Shot 2018-07-11 at 1.23.26 PM.png 88.1 KB View Download

Deleted: Screen Shot 2018-07-11 at 1.24.53 PM.png 58.9 KB

	Screen Shot 2018-07-11 at 1.24.53 PM.png 58.9 KB View Download