Skip to content

Handling hop1 queryids with anydoc #18

Description

@arunchaganty

When developing a KBP system, we often predict provenances for hop0 entities that haven't been seen in the evaluation dataset. The CS-GenerateQueries script generates query ids that depend on the provenance and hence produce new query ids that are not comparable with those in the evaluation data.

Is it possible to handle this issue in the CS-Score script?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions