Triple
T15804033
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rosh Hashanah Musaf service |
E383166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | High Holy Day liturgy |
C36526
|
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: High Holy Day liturgy Context triple: [Rosh Hashanah Musaf service, instanceOf, High Holy Day liturgy]
-
A.
Divine Liturgy
The Divine Liturgy is the central Eucharistic worship service in Eastern Christian traditions, in which the faithful gather to offer praise, thanksgiving, and sacramental communion with God.
-
B.
liturgical solemnity
A liturgical solemnity is the highest-ranking type of feast in the Christian liturgical calendar, marked by special prayers, readings, and rituals that celebrate the most important mysteries of faith or principal saints.
-
C.
Eucharistic liturgy
The Eucharistic liturgy is the structured Christian worship service centered on the celebration of the Eucharist, in which Scripture is proclaimed, prayers are offered, and bread and wine are consecrated and shared as the sacramental presence of Christ.
-
D.
liturgical feast day
A liturgical feast day is a designated date in a religious calendar set apart for the formal celebration and commemoration of a specific sacred event, person, or mystery through prescribed worship and rituals.
-
E.
Eucharistic service
A Eucharistic service is a Christian worship ceremony centered on the consecration and sharing of bread and wine as the sacramental remembrance and participation in the life, death, and resurrection of Jesus Christ.
- F. None of above. chosen
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_69d86da2858c819090cc8481e7207b6e |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:48 a.m.