4 ms·
DBpedia Ontology
- yourapostasy 4y agoI wonder how much cross-pollination with Cyc [1] can be performed, and how DBpedia's ~5M terms can be compared to Cyc's ~25M assertions? [1] https://en.wikipedia.org/wiki/Cyc https://en.wikipedia.org/wiki/Cyc
- deleted 4y ago[deleted]
- mark_l_watson 4y agoI had an example on my blog about 10 years ago blending OpenCyc as OWL/RDF with SPARQL queries to DBPedia (using SERVICE operator). At least for me, this is at best a clumsy process.
- jraph 4y agoRelated: Ontolex [1], an ontology for lexicons. Which DBnary [2], an RDF extract of the Wiktionary, uses. I worked on it almost 10 years ago during an internship during which I added support for extracting French inflections in the DBnary extractor. A colleague did German. It increased the size of DBnary a lot so it was an optional feature. I don't know the status of the project today. Back then, DBnary was based on the Lemon ontology, which apparently Ontolex extends and Ontolex is now a W3C standard, yay! I don't quite use such ontologies in my daily life knowingly, but I find them fascinating for some unknown reasons. [1] https://www.w3.org/2016/05/ontolex/ https://www.w3.org/2016/05/ontolex/ [2] http://kaiko.getalp.org/about-dbnary/ http://kaiko.getalp.org/about-dbnary/
- nerdponx 4y agoI've seen a handful of threads and articles in the last year or so about knowledge graphs, but I still don't understand what they're used for. I understand the idea, I think, but I don't know what problems they actually solve. When would I want to consider building a knowledge graph, or using an existing one in a project?
- lufte 4y agoI would say they are useful, specially against a relational database, when you have a ever-growing or dynamic amount of different entity types that are all related between each other. With a knowledge graph you only don't need to create new tables every time you define new entity types, you also can give semantic meaning to the relationships between them.
- nighthawk454 4y agoI think they can be good for factual queries and entity relations. One example is the Google Knowledge Graph which they use in Search [1]. [1] https://en.wikipedia.org/wiki/Google_Knowledge_Graph https://en.wikipedia.org/wiki/Google_Knowledge_Graph
- dr_dshiv 4y agoIt feels a bit like a GOFAI way to teach machines to play chess— through hand-organized human knowledge versus more successful approaches that rely on computational scale. At the same time, it feels like it could give large language models a sense of “truth.”
- zozbot234 4y agoThe "computational scale" approach to semantic networks has been tried - that's pretty much what Freebase was. The Wikidata community refused a direct import of Freebase because the resulting dataset was full of errors; and even today it similarly rejects bot-generated data.
- dr_dshiv 4y agoRight. Makes sense. But then GPT seems like it is on the verge of accomplishing something very similar but in a much more effective way. I wonder if it can use something like this for training or reinforcement learning, for instance.
- 4y ago
- danbruc 4y agoAm I misunderstanding something or are DBpedia and Wikidata essentially trying to do the same thing?
- zozbot234 4y agoThey're not the same thing. DBPedia is trying to extract structured information from the existing versions of Wikipedia, which are segregated by language and licensed under CC-by-sa. Wikidata is a newer project focused on providing high-quality structured data from scratch (labeled in any natural language), with a CC-0 license that's as close as legally possible to releasing them into the public domain.
- macrolime 4y agoDBPedia is extracting data from infoboxes in Wikipedia, but increasingly Wikidata is the source of the data in the infoboxes.
- mark_l_watson 4y agoThey overlap. Wikidata uses generated URIs for entities, properties, etc. that are not human readable readable; they can be resolved by hovering the mouse cursor on the SPARQL endpoint web app or add a pattern to get the label for these URIs. Many of the Knowledge Graph people who I have worked with clearly prefer Wikidata but I am in the other camp: I find it so much easier using the human-readable meaningful URIs for entities, properties, etc. in DBPedia. Yesterday I wrote SPARQL queries for both DBPedia and Wikipedia.
- dr_dshiv 4y agoIs there a good example of what this is useful for? I’d love to see examples of where it is used. What does it do?