The Knowledge &quot;Graph&quot;[1]offers an optional disambiguation parameter you can query with[2]. DuckDuckGo (I swear I&#x27;m not a shill or associated with them!) offers a disambiguation API out-of-the-box and integrates some of the RDF material I mentioned below. Here&#x27;s your &quot;Apple&quot; example[3].<p>Though, based on the amount of data Google has on the average user, and the fact that you have to sign-up to get an API key which is presumably associated with your search history, Gmail history (either any conversations sent from your Gmail account, or any mail you received dispatched from a Gmail account directed at you), they could easily determine if you meant Apple the fruit [you work for the USDA], Apple the company [you&#x27;re an engineer in SF with a User-Agent history that&#x27;s very heavily skewed towards Safari], or etymological basis of Apple, the word [you&#x27;re a linguist], and disambiguate based on aggregate information. I&#x27;d imagine it&#x27;d be pretty trivial to do with their existing advertising profile + visit history of any site that either has Google Analytics or a Doubleclick ad.<p>[1] Again, I struggle to call it a graph, even if it&#x27;s implemented as a GDB on Google&#x27;s end, until the end-user traverses it, it&#x27;s just a Knowledge API.<p>[2] <a href="https:&#x2F;&#x2F;developers.google.com&#x2F;knowledge-graph&#x2F;reference&#x2F;rest&#x2F;v1&#x2F;" rel="nofollow">https:&#x2F;&#x2F;developers.google.com&#x2F;knowledge-graph&#x2F;reference&#x2F;rest...</a> See: `types&#x27;.<p>[3] <a href="http:&#x2F;&#x2F;api.duckduckgo.com&#x2F;?q=apple&amp;format=json&amp;pretty=1" rel="nofollow">http:&#x2F;&#x2F;api.duckduckgo.com&#x2F;?q=apple&amp;format=json&amp;pretty=1</a>