Triple
T33714354
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | apostolic constitution motu proprio |
E863828
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of Catholic Church law |
C45693
|
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: source of Catholic Church law Context triple: [apostolic constitution motu proprio, instanceOf, source of Catholic Church law]
-
A.
ecclesiastical law code
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.
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.
canon law provision
chosen
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.
-
D.
Kirchenrecht
Kirchenrecht ist die Gesamtheit der von einer Kirche gesetzten oder anerkannten Normen, die ihre innere Ordnung, Organisation, Glaubenspraxis und das Verhältnis zu ihren Mitgliedern und anderen Rechtssystemen regeln.
-
E.
source of Byzantine law
A source of Byzantine law is any authoritative origin—such as imperial legislation, ecclesiastical canons, juristic writings, or customary practices—from which the legal norms of the Byzantine Empire were derived and recognized.
- 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_69f34989871c81908682e22a2fe4b829 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:44 a.m.