Triple
T2201881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syriac liturgical year |
E50507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Christian liturgical calendar |
C6300
|
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 calendar Context triple: [Syriac liturgical year, instanceOf, Christian liturgical calendar]
-
A.
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.
-
B.
liturgical calendar
chosen
A liturgical calendar is a structured schedule of religious seasons, feasts, and observances that organizes worship and devotional practices throughout the year.
-
C.
period in the Christian liturgical year
A period in the Christian liturgical year is a distinct, recurring span of time marked by specific theological themes, rituals, and observances that structure the worship and spiritual life of the Church.
-
D.
liturgical season
A liturgical season is a distinct, recurring period in a religious calendar marked by specific themes, rituals, and observances that structure communal worship and spiritual reflection.
-
E.
Eastern Christian liturgy
Eastern Christian liturgy is the traditional, ritualized form of communal worship in Eastern Christian churches, characterized by highly structured prayers, chants, symbols, and sacraments that express and enact the church’s theology and spiritual life.
- 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_69a88b044ab48190add007487680f009 |
completed | March 4, 2026, 7:41 p.m. |
Created at: March 4, 2026, 7:46 p.m.