<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><br></div>=============================<br> RESOURCE ANNOUNCEMENT<br> RELEASE OF sar-graph 1.0<br> http://<a href="http://sargraph.dfki.de">sargraph.dfki.de</a><br>=============================<div><br>The following resource will be released on META-SHARE and is already available as a pre-release at <a href="http://sargraph.dfki.de">http://sargraph.dfki.de</a>.<div><br>A <b>sar-graph</b> is a graph containing linguistic knowledge at syntactic and lexical semantic levels for a given language and target relation. a sar-graph for a targeted relation assembles many linguistic patterns that are used in texts to mention this relation. The term semantically associated relations graph was chosen since the patterns may either express the target relation directly or by expressing a semantically associated relation. The nodes in a sar-graph are either semantic arguments of a target relation or content words (to be more exact, their word senses) needed to express/recognize an instance of the target relation. The nodes are connected by two kinds of edges: syntactic dependency structure relations and lexical semantic relations. Thus they are labelled with dependency-structure tags provided by a parser or lexical-semantic relation tags. A definition can be found in (Uszkoreit and Xu, 2013). The individual patterns are assembled in one graph per target relation for an easier combination of mentions gathered across sentences, but all patterns could also be employed individually. <br><br><b>From Strings to Things <br>SAR-Graphs: A New Type of Resource for Connecting Knowledge and Language</b><br>Hans Uszkoreit and Feiyu Xu (2013) <br>In Proceedings of 1st International Workshop on NLP and DBpedia (NLP&DBPedia), volume 1064, Sydney, NSW, Australia, CEUR Workshop Proceedings, 10/2013<br><br>The current sar-graph version 1.0 contains syntactic dependency relations between content words. In future versions, we will integrate lexical semantic relations between word senses. <div><br></div><div>In the current version, the patterns have been automatically learned by the web-scale version <b>Web-DARE</b> (Krause et al., 2012) of the relation extraction system <b>DARE </b>(Xu et al., 2007) from dependency structures obtained by parsing sentential mentions of the target relation. DARE patterns contain the content words that signal the mentioned (semantically associated) relation and by the syntactic dependencies that combine these words and link them with the phrases representing the arguments of the target relation. Thus, a sar-graph is composed of syntactic dependency graphs. Their edges denote dependency relations. Each edge is labeled with the tag the parser has assigned to the dependency. Vertices come in two flavors: One type of vertices denotes a regular node in a dependency structure, thus it is labeled with a word. Vertices of the second type represent the slots for the arguments of the target relation, instead of a word, they are labeled by the name of the argument, e.g. Person_1. Several dependency parsers have been employed, but the current set of sar-graphs is built from parsing results of the MALT parser.<br><br>Applications of sar-graphs are information extraction, question answering and summarisation. </div><div>The resource might also be useful for research on paraphrases, textual entailment and syntactic variation within a language.<br><br>Release 1.0 has the following properties:<br><br>Language: English <br>Number of target relations: 25<br>Arity of relations: n-ary relations (2≤n≤5)</div><div>Domains of relations: biographic information, corporations, awards<br>Format of patterns: DARE patterns in lemon format and specific xml schema (DTD provided)<br>Format of sar-graphs: specific xml schema (DTD provided)<br>APIs: java api for reading and storing patterns and sar-graphs,<br><span class="Apple-tab-span" style="white-space: pre;"> </span>java api for various use cases: getting and searching for vertex, edge information of a DARE pattern and a sar-graph,<br><span class="Apple-tab-span" style="white-space: pre;"> </span>java api for pattern visualization<br><br><b>Download </b>is available at: <a href="http://sargraph.dfki.de/download.html">http://sargraph.dfki.de/download.html</a></div><div>More <b>statistics</b> are available at: <a href="http://sargraph.dfki.de/statistics.html">http://sargraph.dfki.de/statistics.html</a><br>More <b>references</b> can be found at: <a href="http://sargraph.dfki.de/publications.html">http://sargraph.dfki.de/publications.html</a><div><b>Feedback</b> via email: <a href="mailto:sargraph@dfki.de">sargraph@dfki.de</a></div><div><br></div><div>sar-graphs were conceived and defined at DFKI LT-Lab Berlin and then realized in </div><div>a collaboration between DFKI LT-Lab and the BabelNet group at Sapienza University of Rome.</div><div><br>The development of sar-graphs is partially supported by <br><div><span class="Apple-tab-span" style="white-space: pre;"> </span>• the German Federal Ministry of Education and Research (BMBF) through the project Deependance (contract 01IW11003)<br></div><div><span class="Apple-tab-span" style="white-space: pre;"> </span>• the project LUcKY, a Google Focused Research Award in the area of Natural Language Understanding. </div></div><div><br></div><div><br></div><div>Enjoy!</div></div></div></div><div apple-content-edited="true">
<span class="Apple-style-span" style="border-collapse: separate; border-spacing: 0px;"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><br></div><div><br></div><div>Feiyu Xu</div><div><br></div><div><br></div><div><br class="Apple-interchange-newline">----------------------------------</div><div>Dr. Feiyu Xu</div><div><br></div><div>Senior Researcher</div><div>Project Leader</div><div><br></div><div>DFKI Projektbüro Berlin</div><div>Alt Moabit 91c</div><div>D-10559 Berlin</div><div>Germany<br>Phone +49-30-<span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif; line-height: 18px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">23895</span>-1812<br>Sek +49-30-<span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif; line-height: 18px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">23895</span>-1800<br>Fax +49-30-<span class="Apple-style-span" style="font-family: Arial, Helvetica, sans-serif; line-height: 18px; -webkit-border-horizontal-spacing: 2px; -webkit-border-vertical-spacing: 2px; ">23895</span>-1810</div><div><br class="webkit-block-placeholder"></div><div><br></div><div>E-mail: <a href="mailto:feiyu@dfki.de">feiyu@dfki.de</a></div><div><br class="webkit-block-placeholder"></div><div>homepage: <a href="http://www.dfki.de/~feiyu">http://www.dfki.de/~feiyu</a></div><div><br class="webkit-block-placeholder"></div><div><br class="webkit-block-placeholder"></div><div>------------------------------------------------------------</div><div><br class="webkit-block-placeholder"></div><div>Deutsches Forschungszentrum fuer Kuenstliche Intelligenz GmbH</div><div>Firmensitz: Trippstadter Strasse 122, D-67663 Kaiserslautern</div><div>Geschaeftsfuehrung:</div><div>Prof. Dr. Dr. h.c. mult. Wolfgang Wahlster (Vorsitzender)</div><div>Dr. Walter Olthoff</div><div><br class="webkit-block-placeholder"></div><div>Vorsitzender des Aufsichtsrats:</div><div>Prof. Dr. h.c. Hans A. Aukes</div><div><br class="webkit-block-placeholder"></div><div>Amtsgericht Kaiserslautern, HRB 2313</div><div><br class="webkit-block-placeholder"></div><div>------------------------------------------------------------</div><div><br class="webkit-block-placeholder"></div></div><div><br></div></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></div></span><br class="Apple-interchange-newline"></span><br class="Apple-interchange-newline"></span>
</div>
<br></body></html>