Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wrong date extractions #22

Open
jure opened this issue Jun 28, 2013 · 0 comments
Open

Wrong date extractions #22

jure opened this issue Jun 28, 2013 · 0 comments

Comments

@jure
Copy link

jure commented Jun 28, 2013

Example 1:

@sciencemagazine is stuck in the 19th century, when it made sense to reject 95% of submissions" - @plos cofounder @mbeisen cc #wcsj2013 wrongly extracts to 19th of July 2013

SUTime is correct:

the 19th century    19XX    <TIMEX3 tid="t1" value="19XX" type="DATE">the 19th century</TIMEX3>
2013    2013    <TIMEX3 tid="t2" value="2013" type="DATE">2013</TIMEX3>

Example 2:
Withings commercially launches Pulse, its first activity tracker http://t.co/bbKAf37veT wrongly extracts to 1st of July 2013

SUTime is correct:
No temporal expressions.

Example 3:
excellent RT @nickbarnes: Gave 1st talk at SoundSoftware 2013: "10 Reasons you must publish your code". Pulled no punches. #openscience wrongly extracts to 1st of July 2013

SUTime is correct:
2013 2013 <TIMEX3 tid="t1" value="2013" type="DATE">2013</TIMEX3>

Example 4:
Been listening to the Vampires of the Modern City album for the past few weeks, and it's absolutely fantastic. #vampireweekend wrongly extracts to 30th of June 2013

SUTime is correct:
the past few weeks PXW <TIMEX3 tid="t1" value="PXW" type="DURATION">the past few weeks</TIMEX3>

I'll soon be in a position to provide a database of these wrong classifications, would that be helpful?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant