2019
DOI: 10.1007/978-3-030-29908-8_39
|View full text |Cite
|
Sign up to set email alerts
|

SPARQL Queries over Ontologies Under the Fixed-Domain Semantics

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Year Published

2022
2022
2022
2022

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(2 citation statements)
references
References 19 publications
0
2
0
Order By: Relevance
“…SPARQL is a query language used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. In recent years, the conversion of natural language questions (NLQs) to SPARQL queries gained further popularity to the growing number of graph-based applications [1]- [3]. Automatic query generation from NLQ is a long-standing research challenge with several factors contributing to its difficulty, including but not limited to understanding the complex aspects of syntax and semantics of the natural language question (i.e., ellipsis, ambiguity, lexical gap), error propagation in NLP pipelines, and skewed distribution of question types in training datasets.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…SPARQL is a query language used to express queries across diverse data sources, whether the data is stored natively as RDF or viewed as RDF via middleware. In recent years, the conversion of natural language questions (NLQs) to SPARQL queries gained further popularity to the growing number of graph-based applications [1]- [3]. Automatic query generation from NLQ is a long-standing research challenge with several factors contributing to its difficulty, including but not limited to understanding the complex aspects of syntax and semantics of the natural language question (i.e., ellipsis, ambiguity, lexical gap), error propagation in NLP pipelines, and skewed distribution of question types in training datasets.…”
Section: Introductionmentioning
confidence: 99%
“…(1) SPARQL templates are usually created manually or semiautomatically by domain experts, which is both time consuming and cost intensive, (2) The query templates are tailored to a particular KG, which results in potentially changing of the whole template set when the underlying graph is changed, (3) The extension of template sets to handle new question types is performed manually or semi-automatically, and (4) In pipeline-based approaches, the SPARQL generation module is dependent on the performance of the preceding modules (i.e., entity and relation linkers as well as ranking algorithms) and, thus, suffer from error propagation.…”
Section: Introductionmentioning
confidence: 99%