Triple

T19688038
Position Surface form Disambiguated ID Type / Status
Subject Anastasis E472762 entity
Predicate isLiturgicallySignificantFor P85852 FINISHED
Object Holy Week observances 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: Holy Week observances | Statement: [Anastasis, isLiturgicallySignificantFor, Holy Week observances]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: isLiturgicallySignificantFor
Context triple: [Anastasis, isLiturgicallySignificantFor, Holy Week observances]
  • A. hasLiturgicalImportance chosen
    Indicates that something holds recognized significance or special status within religious worship or liturgical practice.
  • B. hasLiturgicalNature
    Indicates that something possesses a liturgical character or function, typically relating to formal religious worship or rites.
  • C. hasLiturgicalMention
    Indicates that one entity is referenced or mentioned within the liturgical texts, practices, or rites associated with another entity.
  • D. hasLiturgicalContext
    Indicates that something is associated with, used in, or relevant to a formal religious or liturgical setting or practice.
  • E. isPartOfLiturgicalUnit
    Indicates that one element belongs to, and functions as a component within, a larger liturgical unit or structure.
  • 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_69d8e515bef88190bc30781aea50537a completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e6420d39688190ad3a84dbffce4ffe completed April 20, 2026, 3:11 p.m.
PD Predicate disambiguation batch_69e53039ea808190a9106a53f564ab92 completed April 19, 2026, 7:42 p.m.
Created at: April 10, 2026, 1:45 p.m.