< Home

TitleCategoryDescriptionCreated at Maintainer

21-24 / 24 show all
SRDF 1.0Other Description SRDF is a Korean Open Information Extraction system. It is designed to meet the characteristics of Korean and extract multiple relationships between argument(s) and relation(s) within a sentence by using reificaion technique(specifically, singleton property method). It takes a sentence and produces a set of reified triples on lexical format. Scope and limit The current version covers sentences composed from 3 to 10 words. To eliminate restriction of word length, a new version is being developed. References 1. Sangha Nam, et. al., "SRDF: Korean Open Information Extraction using Singleton Property", ISWC (Poster) 2015.2015-11-05 07:44:01 UTCnam.sangha@gmail.com
AGDISTIS-KODisambiguation # Description Disambiguator uses the AGDISTIS web service to disambiguate URIs for class, property and resources, and then maps them within the result of Templator. So, for the Korean Disambiguator, anyone can use this module. I/O is exactly same with AGDISTIS-en. # Function AGDISTIS-ko works as a sub-module of Disambiguator. It works to disambiguate the URIs for each entities. # Scope and limit Currently (March, 2016), AGDISTIS-ko's algorithm is exactly same with AGDISTIS-en's. It works for Korean, and disambiguates entites within DBpedia URIs # Issues and discusion * Do you want to develop Korean Disambiguator? If you want, there are two remaining development issue. 1. The NER module including this processe: NER and generate the output as well as the input of AGDISTIS-ko (you can see the example) 2. The Wrapper module: Input: Templator output Output: Disambiguator output * How to run the service $ cd /home/b11_2015/AGDISTIS-ko/AGDISTIS $ mvn exec:java Maintainer: Younggyun Hahm {hahmyg@kaist.ac.kr}2015-08-28 06:30:36 UTCzakria.ai@gmail.com
TGM v1Template generation Description Templator is a module for dependency-driven SPARQL template generation from natural language. Templator takes in a question and generates pseudo-queries as well as a list of strings (so-called slots) for which data from the knowledge base is needed. Approach First, the question is linguistically analysed, annotating it with part-of-speech tags, dependency relations, and semantic role labels. Second, the resulting parse tree is transformed into a template, covering one possibility of the how natural language expressions correspond to constructs in the target SPARQL query. This is the template that is most faithful to the linguistic structure of the question. In order to also account for structural differences between the question and the target query, the template is modified by a sequence of steps that collapse or expand triples, yielding additional templates. The scoring of the templates follows a simple heuristics computing the number of nodes in the query body that are neither projection variables nor slots. In addition, each rewriting operation reduces the score by a predetermined factor. Function 1. NLP tools (e.g. the stanford parser) analyze the input question text into dependency parse tree. 2. Then Templator generates the pseudo query for SPARQL query based on the RULEs within dependency parse tree Scope and limit Current version (March, 2016) focused on the hand-crafted RULEs for dependency parse tree. So that the QA performance depends on the RULEs' quality and coverage. Issues and discusion * How to check/add/edit RULEs? ~/src/main/resources/rules/ - RULEs for English: SRL_rules_en.json - RULEs for Korean: SRL_rules_ko.json At this time (January 13, 2016, at OKBQA 3.5) we can not provide yet the web service to add/edit exist RULEs or use your own RULEs for the OKBQA platform. This web service would be provided before/during OKBQA 4 (http://4.okbqa.org) We believe that good RULEs would improve overall performance of (our/your own) QA system. * Does it works for Korean? It currently works for English and Korean. Yes. We've added simple RULEs for some Korean question words such as "무엇", "누구", "어떤", and "얼마나 많". Of course, this rules cover few cases. Now you can test this sentence: "어떤 강이 서울을 흐르는가?" using the following Sample curl command. * How to deploy it: $ git clone https://github.com/okbqa/templator $ cd templator $ mvn compile exec:java Source code Implementations are available on GitHub: github.com/okbqa/templategeneration github.com/okbqa/templator Contacts While general questions about Templator should be addressed to the original developer, Christina Unger {cunger@cit-ec.uni-bielefeld.de}, Younggyun Hahm {hahmyg@kaist.ac.kr} also can act as a contact point especially for the matter on Korean applications. 2015-08-28 01:21:29 UTCcunger@cit-ec.uni-bielefeld.de
SparqlatorQuery generation Description It is a wrapper to call the GraphFinder::sparqlator method, using the OKBQA framework API. It takes a template and a disambiguation structures which are produced by a template generation and a disambiguation modules, respectively, and produces a set of SPARQL queries which are supposed to represent the same query need represented by the template and disambiguation. Optionally, the parameter, max_hop may be set to specify the number of maximum hops for each path to be extended to. As it is to specify an integer value (between 1 and 3, usually), it may be simply encoded in the URL (see Web service URL example below). GraphFinder implements the triple variation operations proposed by [1]. Scope and limit The current version implements only the three operations, inversion, split, and instantiation, among the four proposed in [1]. Implementation of the last one, join is remained as a future work. Language dependency GraphFinder is language-independent, and so does the sparqlator module. References Jin-Dong Kim and Kevin Bretonnel Cohen, “Triple Pattern Variation Operations for Flexible Graph Search”, Proceedings of the 1st international workshop on Natural Language Interfaces for Web of Data (NLIWoD), 2014. 2015-08-28 00:33:26 UTCjindong.kim@gmail.com