Triple
T36306272
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Constitutions and Statutes of the Congregation of the Most Holy Redeemer |
E893950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic canonical document |
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: Catholic canonical document Context triple: [Constitutions and Statutes of the Congregation of the Most Holy Redeemer, instanceOf, Catholic canonical document]
-
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.
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.
-
C.
Catholic reference work
A Catholic reference work is a comprehensive resource that systematically presents information on Catholic doctrine, history, liturgy, canon law, and related topics for study, teaching, and consultation.
-
D.
Vatican instruction
A Vatican instruction is an official document issued by the Holy See that provides authoritative guidelines on the interpretation and practical implementation of Church doctrine, discipline, or liturgical norms.
-
E.
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.
- 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_69f76e4c1b248190b10667d0213537fe |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.