Triple

T968046
Position Surface form Disambiguated ID Type / Status
Subject Burial of Jesus E20880 entity
Predicate hasRitualAction P4193 FINISHED
Object wrapping of Jesus’ body in linen 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: wrapping of Jesus’ body in linen | Statement: [Burial of Jesus, hasRitualAction, wrapping of Jesus’ body in linen]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRitualAction
Context triple: [Burial of Jesus, hasRitualAction, wrapping of Jesus’ body in linen]
  • A. hasRitual chosen
    Indicates that an entity performs, observes, or is associated with a specific ritual or ceremonial practice.
  • B. hasRitualObject
    Indicates that an entity possesses, uses, or is associated with an object specifically employed in a ritual or ceremonial context.
  • C. hasLifecycleRitual
    Indicates that an entity is associated with a ritual or ceremonial practice marking a significant stage or transition in its lifecycle.
  • D. ritualSpecialist
    Indicates that one entity serves as a designated expert or practitioner responsible for performing or overseeing rituals in relation to another entity or context.
  • E. hasSacredSymbol
    Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
  • F. None of above.

Provenance (3 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_69a493b33d2c81909c52c369d3ca8436 completed March 1, 2026, 7:29 p.m.
NER Named-entity recognition batch_69a4b43549008190a4d65efdc3bda520 completed March 1, 2026, 9:48 p.m.
PD Predicate disambiguation batch_69a4b2a579888190afb489ac9fe8391c completed March 1, 2026, 9:41 p.m.
Created at: March 1, 2026, 7:40 p.m.