Live data from Hacker News

$199 Brings Google Knowledge Graph in Reach of Hackers and Startups

basekb.com

1–10 of 27 posts

Re: $199 Brings Google Knowledge Graph in Reach of Hackers and Startups

#3
post #2

Seem's like it might be a better model to charge per # of fact usages (similar to EC2 hourly usage, DB queries, etc)?

The economical (and successful) model for handling data of this sort is batch processing, possibly with some tool like Hadoop -- and our market research shows that many potential customers are already using this.

If we provided a live database to customers we'd have to make at least 10 times the revenue in order to cover variable costs and I'm not sure we could provide a service with satisfying performance at that level.

RDF technology is rapidly advancing and there's no substitute right now for a customer providing his triple store on his own machine with a lot of RAM and a few SSD drives.

Re: $199 Brings Google Knowledge Graph in Reach of Hackers and Startups

#5

What exactly is the difference between using this and the freebase api? Are they just converting data formats?

The difference between SPARQL 1.1 and MQL (the propreitary Freebase language) is like the difference between chess and checkers.

In SPARQL you can write queries that involve any graph relationships that come into your head. You can take the UNION of multiple graph patterns. With SPARQL you can also get back 200,000 or more results.

With MQL you quickly run into the wall when you find that you can't write the query you want (you need to write 10,000 queries instead of one) or that the query you want to run times out, or that it only lets you get back a limited number of answers.

It's also possible to do batch processing with :BaseKB Pro with extreme efficiency. We did a calculation that would have taken 100 years on the biggest machine in the AMZN cloud in SPARQL in just 24 hours on a mac book pro with an optimized pipeline.

Re: $199 Brings Google Knowledge Graph in Reach of Hackers and Startups

#7

What exactly is the difference between using this and the freebase api? Are they just converting data formats?

The difference between SPARQL 1.1 and MQL (the propreitary Freebase language) is like the difference between chess and checkers. In SPARQL you can write queries that involve any graph relationships that come into your head. You can take the UNION of multiple graph patterns. With SPARQL you can also get back 200,000 or more results. With MQL you quickly run into the wall when you find that you can't write the query yo…

How about the Freebase quad dump? Can't I just import that into virtuoso and do the same sparql queries?

Re: $199 Brings Google Knowledge Graph in Reach of Hackers and Startups

#8
post #7

Earlier quoted context omitted.

The difference between SPARQL 1.1 and MQL (the propreitary Freebase language) is like the difference between chess and checkers. In SPARQL you can write queries that involve any graph relationships that come into your head. You can take the UNION of multiple graph patterns. With SPARQL you can also get back 200,000 or more results. With MQL you quickly run into the wall when you find that you can't write the query yo…

How about the Freebase quad dump? Can't I just import that into virtuoso and do the same sparql queries?

The Freebase "quad" dump is not in RDF format, and so cannot be imported into any standard RDF store.

Re: $199 Brings Google Knowledge Graph in Reach of Hackers and Startups

#10
post #9

Freebase isn't the same thing as Google Knowledge graph. Freebase contains 22M entities (according to the wikipedia entry), while the knowledge graph contains 500M entities (according to google announcement).

Actually the 500M (or 400M or 300M) or whatever number is bogus.

We do know that they ported "graphd", the Freebase database, to Google's infrastructure. Really nothing happened at Freebase for a year and a half while they were doing this.

They've probably created a very large Freebase graph for scale testing and it's likely that they're able to handle 500M entities from a hardware perspective.

If you look at how often the GKG comes up in search, it clearly doesn't come up very often. So the process that makes the visible GKG is a process of subtraction, not addition. There are many topics where the GKG could give you an answer from Freebase but it doesn't, and they prune many of them away because they don't want to take the chance of giving wild answers. It's more likely that 1 or 1.5 million topics are in the visible GKG.

Post reply on HN