fix bugs and optimize extraction prompt and parse_fn

[liz-in-tech]

Description

1.fix bugs

The order of "rel" and "obj" in the triple assignment is incorrect.

- subj, rel, obj, description = triple
+ subj, obj, rel, description = triple

2.optimize extraction prompt and parse_fn

Motivation: Different llms exhibit varying capabilities. Through testing with multiple models, I observed that many struggled to comprehend the original output format. Issues included missing parentheses, incorrect numbers of $ symbols, and occasional output of "<" and ">" symbols.

Improvements

• Changed the output format to JSON and provided an output example in the prompt.
• Modified parse_fn to extract entities and relations from JSON strings.
• While most llms still cannot output pure JSON (they tend to include additional content outside the JSON structure), the output consistently contains JSON. Therefore, we implemented a regex to extract the JSON portion.
• This improvements enhances compatibility across different language models while maintaining reliable data extraction.

New Package?

Did I fill in the tool.llamahub section in the pyproject.toml and provide a detailed README.md for my new integration or package?

• Yes
• No

Version Bump?

Did I bump the version in the pyproject.toml file of the package I am updating? (Except for the llama-index-core package)

• Yes
• No

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Your pull-request will likely not be merged unless it is covered by some form of impactful unit testing.

• I added new unit tests to cover this change
• I believe this change is already covered by existing unit tests

Suggested Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added Google Colab support for the newly added notebooks.
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I ran make format; make lint to appease the lint gods

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB