Triple
T6935678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Meatfare Sunday |
E160547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian liturgical observance |
C4017
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Christian liturgical observance Context triple: [Meatfare Sunday, instanceOf, Christian liturgical observance]
-
A.
Christian observance
chosen
A Christian observance is a religious practice, ritual, or commemoration—such as a holiday, sacrament, or liturgical season—through which Christians collectively remember, celebrate, or express key aspects of their faith.
-
B.
Christian religious observance
Christian religious observance is the practice of worship, rituals, and disciplines—such as prayer, sacraments, and holy days—through which Christians express devotion to God and live out their faith in community and daily life.
-
C.
Christian liturgical season
A Christian liturgical season is a distinct, recurring period in the church year marked by specific theological themes, scriptures, prayers, and worship practices that shape the spiritual life and observances of the Christian community.
-
D.
Christian liturgical text
A Christian liturgical text is a written work used in worship services that provides structured prayers, readings, and rituals guiding communal and individual devotion.
-
E.
Eastern Orthodox observance
Eastern Orthodox observance is the collective practice of worship, rituals, fasts, feasts, and traditions that express and sustain the faith and liturgical life of Eastern Orthodox Christians.
- F. None of above.
Provenance (1 batch)
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_69c6884e15208190b9e91487eaafcf85 |
completed | March 27, 2026, 1:38 p.m. |
Created at: March 27, 2026, 2:27 p.m.