Skip to content

LBRON-1364 smart search annotation datamodel#97

Open
tdn wants to merge 3 commits intodevelopmentfrom
feature/LBRON-1364-smart-search-datamodel
Open

LBRON-1364 smart search annotation datamodel#97
tdn wants to merge 3 commits intodevelopmentfrom
feature/LBRON-1364-smart-search-datamodel

Conversation

@tdn
Copy link
Copy Markdown
Contributor

@tdn tdn commented May 8, 2026

To align with the way we store annotations (and reviews) in the HVT (see https://github.com/lblod/frontend-decide-human-validator and https://github.com/lblod/annotation-review-service), we choose to use the Web Annotation Ontology: http://www.w3.org/ns/oa#
In the HVT, oa:Annotation is used in 2 forms:

  1. to store the annotations the AI pipeline makes, as oa:Annotation with a nif:confidence score.
  2. to store the reviews of the annotations, also as oa:Annotation , with the added class of ext:ReviewAnnotation

Each annotation has a target, which in the HVT was limited to resources of class oa:SpecificResource. To accommodate other annotations/reviews though, we need to allow other resource types as target as well. Therefore, we introduce a parent class ext:AnnotationTarget, whch oa:SpecificResource can extend.

For the smart search (UC2), we need to store two types of user feedback:

  1. Feedback (thumbs up/down) on the answer as a whole.
  2. Feedback (thumbs up/down) on the decisions listed as sources for the answer.

To do this, we introduce two new classes to the model that extend ext:AnnotationTarget : schema:Answer and schema:Quotation .

The model for annotations is summarized in the following diagram:
image

notes:
possibly, the LLM should be referenced through prov:wasAssociatedWith ?agent as in https://github.com/lblod/annotation-review-service/blob/master/controllers/annotations.ts#L357 . However, we need to confirm that the question-answering service has the correct agent URI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant