Triple
T25760529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consilium for the Implementation of the Constitution on the Liturgy |
E648728
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | liturgical reform body |
C2440
|
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: liturgical reform body Context triple: [Consilium for the Implementation of the Constitution on the Liturgy, instanceOf, liturgical reform body]
-
A.
liturgical movement
A liturgical movement is a religious reform effort focused on renewing and deepening communal worship practices, texts, and rituals to foster more active and meaningful participation by the faithful.
-
B.
denominational body
A denominational body is an organized religious group or association that represents, governs, and coordinates the beliefs, practices, and activities of congregations within a particular religious denomination.
-
C.
Kirchliches Gremium
Ein kirchliches Gremium ist eine organisierte Gruppe von Personen innerhalb einer Kirche, die gemeinsam Entscheidungen trifft, Beratungsaufgaben wahrnimmt oder bestimmte Verantwortungsbereiche in der kirchlichen Leitung und Verwaltung ausübt.
-
D.
ecclesiastical office-holding body
An ecclesiastical office-holding body is a formally constituted group within a religious organization that collectively holds, administers, or oversees specific church offices, duties, or authorities.
-
E.
theological commission
chosen
A theological commission is a formally appointed group of experts tasked with studying, evaluating, and advising on doctrinal, moral, or ecclesial questions within a religious tradition.
- 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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
Created at: April 22, 2026, 5:05 a.m.