You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@stanbol.apache.org by "Antonio David Pérez Morales (JIRA)" <ji...@apache.org> on 2013/09/13 11:50:56 UTC

[jira] [Comment Edited] (STANBOL-1140) Freebase To Graph Importer

    [ https://issues.apache.org/jira/browse/STANBOL-1140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13720539#comment-13720539 ] 

Antonio David Pérez Morales edited comment on STANBOL-1140 at 9/13/13 9:50 AM:
-------------------------------------------------------------------------------

Freebase importer is a tool to import the Freebase data dump (through BaseKB [1]) into a Graph database managed by Tinkerpop Blueprints [2].  

The aim of this tool is to create a graph with the entity information contained in Freebase in order to be applied in other tasks like graph-based Entity Disambiguation.

The current implementation uses by default the Neo4j graph managed by Tinkerpop (which uses the original Neo4j implementation), because is an indexable and transactionable graph that are two key topics in order to can process the Freebase dump in a manageable time and memory.

The current code can be found at [3].

[1] http://basekb.com
[2] http://blueprints.tinkerpop.com
[3] https://github.com/adperezmorales/gsoc-freebase-graph-importer/tree/master/gsoc-freebase-graph-importer
                
      was (Author: adperezmorales):
    Freebase importer is a tool to import the Freebase data dump (through BaseKB [1]) into a Graph database managed by Tinkerpop Blueprints [2].  

The aim of this tool is to create a graph with the entity information contained in Freebase in order to be applied in other tasks like graph-based Entity Disambiguation.

The current implementation uses by default the Neo4j graph managed by Tinkerpop (which uses the original Neo4j implementation), because is an indexable and transactionable graph that are two key topics in order to can process the Freebase dump in a manageable time and memory.

The current code can be found at [1].

[1] https://github.com/adperezmorales/gsoc-freebase-graph-importer/tree/master/gsoc-freebase-graph-importer
                  
> Freebase To Graph Importer
> --------------------------
>
>                 Key: STANBOL-1140
>                 URL: https://issues.apache.org/jira/browse/STANBOL-1140
>             Project: Stanbol
>          Issue Type: Sub-task
>          Components: Entityhub
>            Reporter: Antonio David Pérez Morales
>              Labels: Freebase, disambiguation, graph, neo4j
>   Original Estimate: 336h
>  Remaining Estimate: 336h
>
> Freebase is a large collaborative knowledge base consisting of metadata composed mainly by its community members. It is an online collection of structured data harvested from many sources, including individual 'wiki' contributions. Freebase aims to create a global resource which allows people (and machines) to access common information more effectively.
> Freebase data is available for free/libre for commercial and non-commercial use under a Creative Commons Attribution License, and an open API, RDF endpoint, and database dump are provided for programmers. Freebase contains 1.2 billion of triples so having this information in a graph will be very useful in order to be able to create new graph-based algorithms for disambiguation.
> The goal of this task is to develop a tool that will be able to parse a Freebase dump and import it in a graph database. For a first version, the selected database will be Neo4j, managed by Tinkerpop Blueprints API. In order to build the graph, we are going to store as vertexes all the Freebase entities. Between two vertex, it will be an edge if there is a direct relationship between both entities in Freebase or a mediated relationship. Mediated relationship relates two entities that are Topics (concepts) in Freebase through an entity that is not a Topic (categories). This categorized edges can be very useful for the later disambiguation.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira