Triple
T1254421
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Usus antiquior |
E26954
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic liturgical rite |
C3535
|
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: Catholic liturgical rite Context triple: [Usus antiquior, instanceOf, Catholic liturgical rite]
-
A.
rite of the Catholic Church
A rite of the Catholic Church is a distinct liturgical, theological, spiritual, and disciplinary tradition by which the Church’s universal faith is expressed and celebrated in worship and practice.
-
B.
form of the Roman Rite
chosen
A form of the Roman Rite is a specific, officially recognized liturgical expression within the Roman Catholic Church’s Roman Rite, characterized by its own texts, rubrics, and ceremonial practices.
-
C.
Oriental Orthodox liturgical rite
An Oriental Orthodox liturgical rite is the structured set of prayers, rituals, and ceremonial actions used in worship within the Oriental Orthodox Churches, reflecting their distinct theological, cultural, and historical traditions.
-
D.
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.
-
E.
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.
- 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_69a49487a9c48190ba9b05348fd1b53f |
completed | March 1, 2026, 7:33 p.m. |
Created at: March 1, 2026, 7:47 p.m.