Matches in ScholarlyData for { ?s ?p ?o. }
- authorList hasItem item-4.
- authorList hasItem item-5.
- authorList hasLastItem item-5.
- item-1 type ListItem.
- item-1 hasContent christian-paul.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent achim-rettinger.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent aditya-mogadala.
- item-3 next item-4.
- item-3 previous item-2.
- item-4 type ListItem.
- item-4 hasContent craig-knoblock.
- item-4 next item-5.
- item-4 previous item-3.
- item-5 type ListItem.
- item-5 hasContent pedro-szekely.
- item-5 previous item-4.
- 207 creator amit-sheth.
- 207 creator gong-cheng.
- 207 creator kalpa-gunaratna.
- 207 creator krishnaprasad-thirunarayan.
- 207 type InProceedings.
- 207 label "Gleaning Types for Literals in RDF Triples with Application to Entity Summarization".
- 207 sameAs 207.
- 207 abstract "Associating meaning with data in a machine-readable format is at the core of the Semantic Web vision, and typing is one such process. Typing (assigning a class selected from schema) information can be attached to URI resources in RDF/S knowledge graphs and datasets to improve quality, reliability, and analysis. There are two types of properties: object properties, and datatype properties. Type information can be made available for object properties as their object values are URIs. Typed object properties allow richer semantic analysis compared to datatype properties, whose object values are literals. In fact, many datatype properties can be analyzed to suggest types selected from a schema similar to object properties, enabling their wider use in applications. In this paper, we propose an approach to glean types for datatype properties by processing their object values. We show the usefulness of generated types by utilizing them to group facts on the basis of their semantics in computing diversified entity summaries by extending a state-of-the-art summarization algorithm.".
- 207 hasAuthorList authorList.
- 207 isPartOf proceedings.
- 207 title "Gleaning Types for Literals in RDF Triples with Application to Entity Summarization".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasItem item-4.
- authorList hasLastItem item-4.
- item-1 type ListItem.
- item-1 hasContent kalpa-gunaratna.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent krishnaprasad-thirunarayan.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent amit-sheth.
- item-3 next item-4.
- item-3 previous item-2.
- item-4 type ListItem.
- item-4 hasContent gong-cheng.
- item-4 previous item-3.
- 219 creator frank-van-harmelen.
- 219 creator stefan-schlobach.
- 219 creator wouter-beek.
- 219 type InProceedings.
- 219 label "A Contextualised Semantics for owl:sameAs".
- 219 sameAs 219.
- 219 abstract "Identity relations are at the foundation of the Semantic Web and the Linked Data initiative. In many instances the classical interpretation of identity is too strong for practical purposes. This is particularly the case when two entities are considered the same in some but not all contexts. Unfortunately, modeling the specific contexts in which an identity relation holds is cumbersome and, due to arbitrary reuse and the Open World Assumption, it is impossible to anticipate all contexts in which an entity will be used. We propose an alternative semantics for owl:sameAs that partitions the original relation into a hierarchy of subrelations. The subrelation to which an identity statement belongs depends on the dataset in which the statement occurs. Adding future assertions may change the subrelation to which an identity statement belongs, resulting in a context-dependent and non-monotone semantics. We show that this more complicated semantics is better able to characterize the pragmatic use of owl:sameAs as observed in Linked Open Datasets.".
- 219 hasAuthorList authorList.
- 219 isPartOf proceedings.
- 219 title "A Contextualised Semantics for owl:sameAs".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasLastItem item-3.
- item-1 type ListItem.
- item-1 hasContent wouter-beek.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent stefan-schlobach.
- item-2 next item-3.
- item-2 previous item-1.
- item-3 type ListItem.
- item-3 hasContent frank-van-harmelen.
- item-3 previous item-2.
- 220 creator ansgar-scherp.
- 220 creator johann-schaible.
- 220 creator thomas-gottron.
- 220 type InProceedings.
- 220 label "TermPicker: Enabling the Reuse of Vocabulary Terms by Exploiting Data from the Linked Open Data Cloud".
- 220 sameAs 220.
- 220 abstract "Deciding which vocabulary terms to use when modeling data as Linked Open Data (LOD) is far from trivial. In this paper, we propose TermPicker: a novel approach enabling vocabulary reuse by recommending RDF types and properties based on various features of a vocabulary term. These features include the term’s popularity, whether it is from an already used vocabulary, and the so-called schema-level pattern (SLP) feature, which exploits how other data providers on the LOD cloud use RDF types and properties to describe their data. We use the machine learning approach Learning To Rank (L2R) to establish a generalized ranking model for vocabulary terms over the utilized features. The results illustrate that using the SLP feature provides an improvement of the recommendation quality by 29 − 36% considering the Mean Average Precision (MAP) and the Mean Reciprocal Rank at the first five positions (MRR@5) compared to recommendations based on solely the term’s popularity and whether it is from an already used vocabulary.".
- 220 hasAuthorList authorList.
- 220 isPartOf proceedings.
- 220 title "TermPicker: Enabling the Reuse of Vocabulary Terms by Exploiting Data from the Linked Open Data Cloud".
- authorList type List.
- authorList hasFirstItem item-1.
- authorList hasItem item-1.
- authorList hasItem item-2.
- authorList hasItem item-3.
- authorList hasLastItem item-3.
- item-1 type ListItem.
- item-1 hasContent johann-schaible.
- item-1 next item-2.
- item-2 type ListItem.
- item-2 hasContent thomas-gottron.