fix: update docling prediction provider to include word cells

[samiuc]

DoclingPredictionProvider returned 0 F1, Recall, and Precision scores during evaluation and upon investigation, I found out that the word cells were not being populated in the SegmentedPage object that OCREvaluator uses for calculating metrics, so added a fix to copy cells from the original page to the parsed_page (SegmentedPage) word cells object.

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🔴 Require two reviewer for test updates

This rule is failing.

When test data is updated, we require two reviewers

• #approved-reviews-by >= 2

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\(.+\))?(!)?:

[cau-git]

This is going to inject fake cells into the word_cells of a parsed_page. The only case in which that is currently a valid case is when the document was fully OCRed, hence this is a very partial workaround.

Also please consider that...

• The standard OCR options in Docling are generating line-level cells (TextCellUnit.LINE), not word-level cells. So this would not compare.
• The parsed_page will be populated from Docling, this code would simply overwrite the word_cells without checking if some are present (they will be present whenever the source PDF hat programmatic cells)

[cau-git]

This is addressed here: docling-project/docling#1745 for consistent line-level cells. Word-level cells cannot be easily retrieved across all OCR backends.

[cau-git]

@samiuc We have released now a docling version where the OCR cells are included in the SegmentedPage (parsed_page) output on the line-level cells.

[github-actions]

✅ DCO Check Passed

Thanks @samiuc, all your commits are properly signed off. 🎉