Triple

T2283023
Position Surface form Disambiguated ID Type / Status
Subject Kriophoros E51321 entity
Predicate hasRitualContext P36127 FINISHED
Object votive offerings for protection of herds LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: votive offerings for protection of herds | Statement: [Kriophoros, hasRitualContext, votive offerings for protection of herds]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRitualContext
Context triple: [Kriophoros, hasRitualContext, votive offerings for protection of herds]
  • A. hasRitual
    Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
  • B. hasRitualRule
    Indicates that an entity is governed by, or associated with, a specific ritual rule or prescribed ceremonial guideline.
  • C. hasRitualSpace
    Indicates that an entity possesses or is associated with a designated space used for ritual or ceremonial activities.
  • D. hasRitualObject
    Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
  • E. hasRitualFocus
    Indicates that an entity is associated with or directed toward a particular object, practice, or element that serves as the central focus of a ritual.
  • F. None of above. chosen

Provenance (4 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69a88b08e4308190bdac9aebcca1c91a completed March 4, 2026, 7:42 p.m.
NER Named-entity recognition batch_69abc21d6d748190980128c1bc5b9621 completed March 7, 2026, 6:13 a.m.
PD Predicate disambiguation batch_69abbdbb9e4c819085fc588626ec7c09 completed March 7, 2026, 5:55 a.m.
PDg Predicate description generation batch_69abbe1ecb7081909c2c66da08a48ab7 completed March 7, 2026, 5:56 a.m.
Created at: March 4, 2026, 7:48 p.m.