anuzzolese / oke-challenge

19 stars 8 forks source link

Issue on start and end position in the task-1 training set #7

Closed jplu closed 9 years ago

jplu commented 9 years ago

Hi,

I spotted another problem with positions:

<http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-90#char=42,53>
        a                     nif:String , nif:RFC5147String ;
        nif:anchorOf          "Charborough"@en ;
        nif:beginIndex        "42"^^xsd:int ;
        nif:endIndex          "53"^^xsd:int ;
        nif:referenceContext  <http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-90#char=0,313> ;
        itsrdf:taIdentRef     oke:Charborough .

Should be:

<http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-90#char=177,189>
        a                     nif:String , nif:RFC5147String ;
        nif:anchorOf          "Charborough"@en ;
        nif:beginIndex        "177"^^xsd:int ;
        nif:endIndex          "189"^^xsd:int ;
        nif:referenceContext  <http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-90#char=0,313> ;
        itsrdf:taIdentRef     oke:Charborough .

Cheers.

anuzzolese commented 9 years ago

This issue was fixed several time ago with the following:

<http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-90#char=177,188>
        a                     nif:String , nif:RFC5147String ;
        nif:anchorOf          "Charborough"@en ;
        nif:beginIndex        "177"^^xsd:int ;
        nif:endIndex          "188"^^xsd:int ;
        nif:referenceContext  <http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-90#char=0,313> ;
        itsrdf:taIdentRef     oke:Charborough .
jplu commented 9 years ago

Thanks for the changes.

I have found a new one between <http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-73#char=184,191> and <http://www.ontologydesignpatterns.org/data/oke-challenge/task-1/sentence-73#char=170,184>

Cheers

rtroncy commented 9 years ago

I guess that this issue should then be re-opened