Triple
T11056321
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anamnesis |
E261385
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Eucharistic Prayer |
C20374
|
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: component of the Eucharistic Prayer Context triple: [Anamnesis, instanceOf, component of the Eucharistic Prayer]
-
A.
section of the Eucharistic Prayer
chosen
A section of the Eucharistic Prayer is a distinct liturgical unit within the central prayer of the Mass that expresses a specific theological or ritual function, such as praise, thanksgiving, consecration, or intercession.
-
B.
element of the Roman Catholic Mass
An element of the Roman Catholic Mass is a distinct liturgical component—such as a prayer, ritual action, or proclamation—that together with other elements forms the structured celebration of the Eucharist.
-
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.
part of the Roman Canon
A "part of the Roman Canon" is a distinct textual or structural segment within the central Eucharistic prayer of the traditional Roman Rite of the Catholic Mass.
-
E.
part of the Catholic Mass
A part of the Catholic Mass is a distinct liturgical segment, such as the Liturgy of the Word or the Eucharistic Prayer, that together with other segments forms the complete celebration of the Eucharist.
- 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_69d6aa98650481908609c7c56bfa7902 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:26 p.m.