Triple
T11120307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apostolic Constitution Regimini Ecclesiae Universae |
E262997
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | document of the Roman Catholic Church |
C6247
|
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: document of the Roman Catholic Church Context triple: [Apostolic Constitution Regimini Ecclesiae Universae, instanceOf, document of the Roman Catholic Church]
-
A.
Catholic Church document
chosen
A Catholic Church document is an official written text issued or approved by Church authority that communicates, clarifies, or governs matters of faith, morals, liturgy, or discipline.
-
B.
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.
-
C.
ecclesiastical document
An ecclesiastical document is an official written instrument issued or authorized by a church authority that records, communicates, or regulates matters of faith, doctrine, worship, or church governance.
-
D.
Roman Catholic church
A Roman Catholic church is a Christian place of worship that serves as a local community’s center for liturgy, sacraments, and prayer within the Roman Catholic tradition.
-
E.
office in the Catholic Church
An office in the Catholic Church is an established position of ecclesiastical responsibility, authority, or service, entrusted to a person for the governance, ministry, or administration of the Church.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:28 p.m.