Triple
T29619256
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Book IV: The Sanctifying Function of the Church |
E754949
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | book of the 1983 Code of Canon Law |
C2706
|
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: book of the 1983 Code of Canon Law Context triple: [Book IV: The Sanctifying Function of the Church, instanceOf, book of the 1983 Code of Canon Law]
-
A.
ecclesiastical law code
chosen
An ecclesiastical law code is a systematic collection of rules and regulations issued by a religious authority to govern the doctrine, discipline, and organizational life of a church or religious community.
-
B.
canon law provision
A canon law provision is a specific, authoritative rule or norm established by a competent ecclesiastical authority to regulate conduct, governance, and doctrine within the Church’s legal system.
-
C.
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.
-
D.
Gallican statement
A Gallican statement is a doctrinal or legal assertion expressing the principles of Gallicanism, typically emphasizing the relative independence of the French Church and monarchy from papal authority.
-
E.
topic in canon law
A topic in canon law is a specific subject area or issue governed by the Church’s legal system, encompassing the rules, principles, and procedures that regulate ecclesiastical life and governance.
- 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_69f0ef86b6ec8190a87fff07fd983b1e |
completed | April 28, 2026, 5:33 p.m. |
Created at: April 28, 2026, 6:33 p.m.