Query test for Fraunhofer SCAI UIMA-HPC

Statement: 
Display all documents. A limit of result per page $number$ (e.g.10)
Query: 
SELECT ?coveredText2 WHERE { ?hit <http://purl.org/ao/context> ?section . ?run <http://purl.org/ao/item> ?hit . ?hit <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.scai.fraunhofer.de/prominer/vocabular/pao#Section> . ?run <http://purl.org/ao/item> ?section . ?hit <http://purl.org/ao/hasTopic> <http://www.scai.fraunhofer.de/rdf/PatentSegmenterAE/SUMMARY> . ?run <http://www.w3.org/ns/prov#wasGeneratedBy> <http://www.scai.fraunhofer.de/rdf/entity/PatentSegmenter> . ?hit <http://purl.org/ao/onSourceDocument> ?document . ?section<http://purl.org/ao/selectors/exact> ?coveredText . ?section <http://nlp2rdf.lod2.eu/schema/string/beginIndex> ?begin_synth . ?section <http://nlp2rdf.lod2.eu/schema/string/endIndex> ?end_synth . ?hit2 <http://purl.org/ao/context> ?chemistry_ProMiner . ?hit2 <http://www.w3.org/1999/02/22-rdf-syntax-ns#type> <http://www.scai.fraunhofer.de/prominer/vocabular/pao#NormalizedNamedEntity> . ?run2 <http://purl.org/ao/item> ?hit2 . ?run2 <http://purl.org/ao/item> ?chemistry_ProMiner . ?run2 <http://www.w3.org/ns/prov#wasGeneratedBy> <http://www.scai.fraunhofer.de/rdf/entity/CNER> . ?hit2 <http://purl.org/ao/onSourceDocument> ?document . ?chemistry_ProMiner <http://nlp2rdf.lod2.eu/schema/string/beginIndex> ?begin_synth2 . ?chemistry_ProMiner <http://nlp2rdf.lod2.eu/schema/string/endIndex> ?end_synth2 . ?chemistry_ProMiner <http://purl.org/ao/selectors/exact> ?coveredText2 . FILTER(?begin_synth2>=?begin_synth && ?end_synth2<=?end_synth ) . } Limit ??number

Comments

María Jesús's picture

Hi, Firstly, we want to thank you for using our application; we are creating a user community to warrant its working collaboratively so, your contribution is welcomed. we had some problems but now, all is fixed and works. We have published the problematic query as you can see above ("Query test for Fraunhofer SCAI UIMA-HPC" ) then, you can edit or execute it. Best, Bioqueries team.

Thanks a lot, it's working as expected now!