glam/schemas/20251121/linkml/modules/classes/SpecificityAnnotation.yaml
kempersc 4319f38c05 Add archived slots for audience size, audience type, and capacity metrics
- Created new YAML files for audience size and audience type slots, defining their properties and annotations.
- Added archived capacity slots including cubic meters, linear meters, item count, and descriptions, with appropriate URIs and ranges.
- Introduced a template specificity slot for context-aware RAG filtering.
- Consolidated capacity-related slots into a unified structure, including has_or_had_capacity, capacity_type, and capacity_value, with detailed descriptions and examples.
2026-01-17 18:53:23 +01:00

61 lines
2.1 KiB
YAML

id: https://nde.nl/ontology/hc/class/SpecificityAnnotation
name: SpecificityAnnotation
title: Specificity Annotation
prefixes:
linkml: https://w3id.org/linkml/
hc: https://nde.nl/ontology/hc/
prov: http://www.w3.org/ns/prov#
skos: http://www.w3.org/2004/02/skos/core#
default_prefix: hc
imports:
- linkml:types
- ./TemplateSpecificityScore # was: TemplateSpecificityScores - migrated per Rule 53 (2026-01-17)
- ./TemplateSpecificityType
- ./TemplateSpecificityTypes
- ../slots/specificity_agent
- ../slots/specificity_rationale
- ../slots/specificity_score
- ../slots/specificity_timestamp
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ../slots/specificity_agent
- ../slots/specificity_rationale
- ../slots/specificity_score
- ../slots/specificity_timestamp
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
- ../slots/specificity_agent
- ../slots/specificity_rationale
- ../slots/specificity_score
- ../slots/specificity_timestamp
- ../slots/has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
classes:
SpecificityAnnotation:
class_uri: hc:SpecificityAnnotation
description: 'Structured metadata for RAG retrieval specificity scoring.
Documents how specific/general a class is for different search templates.
**Scoring Semantics** (LOWER = more broadly relevant):
- 0.00-0.20: Universal (HeritageCustodian, Location)
- 0.20-0.40: Broadly useful (Collection, Identifier)
- 0.40-0.60: Moderately specific (ChangeEvent, PersonProfile)
- 0.60-0.80: Fairly specific (Archive, Museum, Library)
- 0.80-1.00: Highly specific (LinkedInConnectionExtraction)
'
slots:
- specificity_score
- specificity_rationale
- specificity_timestamp
- specificity_agent
- has_or_had_score # was: template_specificity - migrated per Rule 53 (2026-01-17)
annotations:
specificity_score: 0.2
specificity_rationale: Meta-class for specificity annotations