-
Notifications
You must be signed in to change notification settings - Fork 60
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
different error arisen sometimes #22
Comments
Hello, Thank you for pointing out this issue. |
Thanks for your relpy! itext2kg-0.0.7. I think it's the latest version. thank you |
Hi, I'm meeting the same issue when trying to construct the KG for the second job offer It gives this error: "[INFO] ------- Extracting Entities from the Document 2 As it expects the "name" field to be string but get "list" of str. |
I had the same problem running "kg_ = itext2kg.build_graph(sections=[semantic_blocks_job_offer, semantic_blocks_job_offer_2], existing_knowledge_graph=kg, ent_threshold=0.6, rel_threshold=0.6)" with llama3:ValidationError: 1 validation error for Entity |
Hello, The major problem of these local and small models is their inability to structure the output. But, we will consider this issue in our next releases ;) |
I ran the example notebook using one of the CVs provided. I try to build graph for the cv and two job offers.
I build graph for the cv succesfully most of the time, but TypeError is arisen sometimes.
itext2kg/irelations_extraction/irelations_extractor.py, line 96.
'relationship' is supposed to be a dict, but it's a str sometimes.
I tried to build graph for the twe job offers so many times and succeeded only once.
a. Same problem as above, part of relation extractor
b. I often fail when try to extracte entities for the second text of the job offer. /itext2kg/itext2kg.py, line 85
/itext2kg/ientities_extraction/ientities_extractor.py, line 71.
the para 'name' is supposed to be a str, but it could be a list sometimes.
I think the reason for these problems has something to do with the model I'm using, llama3-8b, because the semantic block, entities and relations I got using this model are not always the same. But I think these problems(unexpected type) should be considered.
Thanks for your patient.
The text was updated successfully, but these errors were encountered: