Triple
T10305016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Iuris Canonici |
E241729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | source of Roman Catholic 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: source of Roman Catholic canon law Context triple: [Corpus Iuris Canonici, instanceOf, source of Roman Catholic canon law]
-
A.
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.
-
B.
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.
-
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.
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.
-
E.
part of the Roman Canon
A "part of the Roman Canon" is a distinct textual or structural segment within the central Eucharistic prayer of the traditional Roman Rite of the Catholic Mass.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:46 a.m.