Triple

T6087815
Position Surface form Disambiguated ID Type / Status
Subject Little Litany E135683 entity
Predicate placementInLiturgy P10005 FINISHED
Object between major sections of the Divine Liturgy 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: between major sections of the Divine Liturgy | Statement: [Little Litany, placementInLiturgy, between major sections of the Divine Liturgy]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: placementInLiturgy
Context triple: [Little Litany, placementInLiturgy, between major sections of the Divine Liturgy]
  • A. usedInLiturgy
    Indicates that something is employed or incorporated as part of a formal religious liturgy or worship service.
  • B. liturgicalUsage chosen
    Indicates how something is used, practiced, or functions within a specific liturgical or worship context.
  • C. liturgicalSetting
    Indicates the specific religious or worship context in which a liturgical text, action, or element is intended to be used.
  • D. usesAlsoLiturgy
    Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
  • E. aimsForLiturgicalUse
    Indicates that something is intended or designed specifically for use in liturgical or formal religious worship contexts.
  • 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_69c0087bcc788190b20f093d3a6c60ec completed March 22, 2026, 3:19 p.m.
NER Named-entity recognition batch_69c0578bf2508190859c2dbd4c10b316 completed March 22, 2026, 8:56 p.m.
PD Predicate disambiguation batch_69c049f3b1ec8190bea67a7bec6442a5 completed March 22, 2026, 7:58 p.m.
Created at: March 22, 2026, 4:12 p.m.