Triple

T25120702
Position Surface form Disambiguated ID Type / Status
Subject Sunday of the Triodion period E629256 entity
Predicate liturgicalTextsSource P74946 FINISHED
Object Triodion NE NERFINISHED

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: Triodion | Statement: [Sunday of the Triodion period, liturgicalTextsSource, Triodion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: liturgicalTextsSource
Context triple: [Sunday of the Triodion period, liturgicalTextsSource, Triodion]
  • A. liturgicalText
    Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices associated with another entity.
  • B. liturgicalTextsFoundIn chosen
    Indicates that certain liturgical texts are located in, originate from, or are associated with a particular place or source.
  • C. hasLiturgicalTexts
    Indicates that an entity possesses or is associated with specific liturgical texts used in religious worship or ceremonies.
  • D. liturgicalMoment
    Indicates the specific point or phase within a liturgical or religious service at which an action, prayer, or ritual occurs.
  • E. liturgicalSequence
    Indicates the ordered progression of rites, prayers, or ceremonies within a liturgical service.
  • 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_69e2ff3288048190bd82c3b7f7bd0e62 completed April 18, 2026, 3:49 a.m.
NER Named-entity recognition batch_69f465ca9a088190911a49d5117b67d8 completed May 1, 2026, 8:35 a.m.
PD Predicate disambiguation batch_69f45cfb53f4819099bba48c5057e787 completed May 1, 2026, 7:57 a.m.
Created at: April 18, 2026, 6:28 a.m.