Triple

T1159064
Position Surface form Disambiguated ID Type / Status
Subject Great Vespers E24453 entity
Predicate hasLiturgicalFunction P10005 FINISHED
Object principal evening worship 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: principal evening worship | Statement: [Great Vespers, hasLiturgicalFunction, principal evening worship]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLiturgicalFunction
Context triple: [Great Vespers, hasLiturgicalFunction, principal evening worship]
  • A. hasLiturgicalCelebration
    Indicates that a religious figure, event, or concept is formally commemorated or observed within a liturgical calendar or worship service.
  • B. hasPrimaryLiturgicalForm
    Indicates that an entity is associated with its main or officially recognized liturgical form used in worship or religious practice.
  • C. hasLiturgicalRank
    Indicates that an entity is assigned a specific status or level within a liturgical or religious ceremonial hierarchy.
  • D. liturgicalUsage chosen
    Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
  • E. hasSecondaryLiturgy
    Indicates that an entity is associated with an additional, subordinate liturgical service or rite beyond its primary liturgy.
  • 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_69a494060e148190abb42f971242c197 completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4bcad47a08190895769611798f67f completed March 1, 2026, 10:24 p.m.
PD Predicate disambiguation batch_69a4bb525b648190adcb7a29256d3c41 completed March 1, 2026, 10:18 p.m.
Created at: March 1, 2026, 7:45 p.m.