-
Notifications
You must be signed in to change notification settings - Fork 19
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
Problem parsing rules in Freebase #21
Comments
Hi, PR #19 broke some experiments of mine (nothing too bad), so I started debugging.
It seems that the numbers are not being parsed correctly (
I've included some tests in PR #22. I hope it helps spotting this things in the future. I'm not so good with regex, so I'd be glad if you checked this issue with numbers. Also, Regards, |
Tests for rule parsing + small bug fix - #21
Hi, The regexp should be fixed (according to @falcaopetri 's test cases, thanks a lot for those). Problem was in URI pattern, @lgalarra removed "\w" that was necessary to match numbers (\p{L} only match letters). |
Hi, I just would like to point out that
|
Hi,
AMIE cannot parse rules such as:
?a /film/actor/film./film/performance/film /m/0340hj => ?a neg_/award/award_nominee/award_nominations./award/award_nomination/award
I have boiled down the problem to the method rules in KB.java. I am proposing a new regex for parsing. We do not supported typed literals on the other hand. My fix is available in #19 .
Cheers,
Luis
The text was updated successfully, but these errors were encountered: