@prefix dc: <http://purl.org/dc/terms/> .
@prefix this: <http://purl.org/np/RATS_1-3zMQUWRacp5VrRlwNfFqRYV3WozEUA2-KPIQ9I> .
@prefix sub: <http://purl.org/np/RATS_1-3zMQUWRacp5VrRlwNfFqRYV3WozEUA2-KPIQ9I#> .
@prefix xsd: <http://www.w3.org/2001/XMLSchema#> .
@prefix prov: <http://www.w3.org/ns/prov#> .
@prefix pav: <http://purl.org/pav/> .
@prefix np: <http://www.nanopub.org/nschema#> .
@prefix linkflows: <https://github.com/LaraHack/linkflows_model/blob/master/Linkflows.ttl#> .

sub:Head {
  this: np:hasAssertion sub:assertion;
    np:hasProvenance sub:provenance;
    np:hasPublicationInfo sub:pubinfo;
    a np:Nanopublication .
}

sub:assertion {
  sub:comment-4 a linkflows:ContentComment, linkflows:NoActionNeededComment, linkflows:PositiveComment,
      linkflows:ReviewComment;
    linkflows:hasCommentText "Authors compare different combinations of worker/expert answers and propose different types of workflows to identify errors in linked data. The paper focuses on 3 specific types of errors. Authors focus exclusively on error identification as fixes can be best applied by correcting the automatic extraction process rather than the generated data.";
    linkflows:hasImpact "4"^^xsd:positiveInteger;
    linkflows:refersTo <http://purl.org/np/RAnVHrB5TSxLeOc6XTVafmd9hvosbs4c-4Ck0XRh_CgGk#articleVersion1> .
}

sub:provenance {
  sub:assertion prov:hadPrimarySource <http://dx.doi.org/10.3233/sw-160239>;
    prov:wasAttributedTo <https://orcid.org/0000-0002-7311-3693> .
}

sub:pubinfo {
  this: dc:created "2019-11-26T09:05:11+01:00"^^xsd:dateTime;
    pav:createdBy <https://orcid.org/0000-0002-7114-6459> .
}