Triple

T29197929
Position Surface form Disambiguated ID Type / Status
Subject Maronite Divine Liturgy E740179 entity
Predicate usesLectionary P5456 FINISHED
Object Maronite lectionary 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: Maronite lectionary | Statement: [Maronite Divine Liturgy, usesLectionary, Maronite lectionary]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesLectionary
Context triple: [Maronite Divine Liturgy, usesLectionary, Maronite lectionary]
  • A. usesLiturgicalCalendar
    Indicates that an entity follows or organizes its religious observances according to a formal liturgical calendar.
  • B. hasLiturgicalReading chosen
    Indicates that a religious service, observance, or liturgical event includes or is associated with a specific prescribed reading from scripture or other sacred text.
  • C. isMaterLectionis
    Indicates that a letter functions as a mater lectionis, i.e., it represents a vowel sound rather than serving as a consonant.
  • D. usesAlsoLiturgy
    Indicates that an entity additionally employs or follows a particular liturgy alongside its primary or other liturgical practices.
  • E. liturgicalText
    Indicates that one entity is a liturgical or ritual text used in the religious or ceremonial practices 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_69f07cb8033c8190b8807e219a14333d completed April 28, 2026, 9:24 a.m.
NER Named-entity recognition batch_69f6a28c7c148190bfc980aad9f678ca completed May 3, 2026, 1:19 a.m.
PD Predicate disambiguation batch_69f69fe1e3c88190830bb2e9f407357e completed May 3, 2026, 1:07 a.m.
Created at: April 28, 2026, 12:05 p.m.