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

Preprocessing - inconsistent tokenization #11

Open
leonardmq opened this issue May 28, 2019 · 0 comments
Open

Preprocessing - inconsistent tokenization #11

leonardmq opened this issue May 28, 2019 · 0 comments

Comments

@leonardmq
Copy link

Hi there,

I used your data_script.py to try and read the ACE dataset. It works pretty well, but many tokens end up not being properly segmented / broken down into tokens, which is even more of an issue considering that a large number of those incorrectly tokenized words are event triggers.

Here are a couple of such examples:

corres pondencebetwee n his estranged wife and partners while she worked at the law firm 's

hamas and other palestinian militias carried out five suicid ebombing s tha tkille d 12 israelis an dwounde d dozens abu amr said the militants apparently unleashed

military support u s officials speaking on the record deny there are firm plans t opul l troops from germany but senior diplomats and officials say privately that it is being

So I've got plenty of event triggers for the word ewa (which I made out is a poorly segmented war), or opoiso (instead of poison) and plenty of similar tokens.

I am suspecting the issue comes from the offset provided by the dataset, which I found to be difficult to work with if not inconsistent.

Did you have similar issues when preprocessing the set?

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