Triple
T10305014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Iuris Canonici |
E241729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collection 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: collection of canon law Context triple: [Corpus Iuris Canonici, instanceOf, collection 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.
collection of ecclesiastical documents
A collection of ecclesiastical documents is an organized set of official church writings—such as decrees, letters, liturgical texts, and doctrinal statements—preserved for reference, governance, and historical record within a religious community.
-
C.
jurisprudence corpus
A jurisprudence corpus is a structured collection of legal texts, such as statutes, case law, and scholarly writings, compiled for analysis, research, and reference in the study and practice of law.
-
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.
set of ecumenical councils
A set of ecumenical councils is a collection of formally convened universal church assemblies recognized for authoritatively defining doctrine, discipline, and responses to major theological or ecclesial controversies.
- 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.