Error when running graphrag.index after enable claim_extraction [Bug]: <title>

[mavershang]

Do you need to file an issue?

• [ ] I have searched the existing issues and this bug is not already filed.
• [ ] My model is hosted on OpenAI or Azure. If not, please look at the "model providers" issue and don't file a new one here.
• [ ] I believe this is a legitimate bug, not just a question. If this is a question, please use the Discussions area.

Describe the bug

After enabled claim_extraction, graphrag_index runs to error in create_final_covariates step. Error as attached. It runs ok if I disable claim_extraction.

Steps to reproduce

No response

Expected Behavior

No response

GraphRAG Config Used

# Paste your config here

Logs and screenshots

No response

Additional Information

• GraphRAG Version:
• Operating System:
• Python Version:
• Related Issues:

[camper-chan[bot]]

Hello,

Firstly, thank you for submitting this pull request!

As you navigate through the process, we have a PR checklist to ensure consistency and quality in our contributions. We kindly ask that you genuinely follow through with each point. This not only facilitates the review process but also demonstrates a mutual respect for the community's efforts.

If you're unfamiliar with certain aspects, our contributing guidelines are a helpful resource to get you up to speed.

**Friendly Pointers (click to expand)**

1. Editing on GitHub: While it's possible to edit files directly on GitHub, it's typically better not to. This helps avoid inadvertent mistakes like typos that can disrupt tests.

2. Pull Request Title: Please ensure the PR title follows our convention.

3. Linking Issues: Please ensure you link issues using the designated method. Simply update the XXXXXX in the PR description to include the issue number. This keeps our records organized and clear.

4. Engaging with the Team: We know you're eager, but kindly keep mentions and review requests limited. Our maintainers are always on the lookout and will attend to PRs in the order they come in.

5. Branch Management: It's a good practice not to work directly off your main branch. Creating separate branches for different changes allows you to smoothly update your PR even as the main repository progresses.

Please note, there's no need to close this PR. If you have questions or need guidance refining your contribution, don't hesitate to ask. Our community is here to assist.

Thank you for your enthusiasm in contributing to our project. We eagerly await more contributions from you!

Happy Contributing! 🌟

[gagan-bhullar-tech]

@moT01 updated PR.