Skip to content

upload to ORKG paper function needs to distinguish between extracted values that are resources versus literals #7

Description

@jd-coderepos

At the moment, the final stage of the workflow uploads all extracted values to ORKG as literals. However, according to the original LLM Catalog comparison (https://orkg.org/comparisons/R1364660), extracted values fall into two categories: resources and literals. The current add_paper function should be extended to distinguish between these types and create ORKG resources for values that are intended to be resources, rather than storing them as literals. Only values corresponding to primitive data should remain literals.

Metadata

Metadata

Assignees

Labels

invalidThis doesn't seem right

Type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions