Triple
T30685602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rivadavia Law of Ecclesiastical Reform |
E781176
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | ecclesiastical reform law |
C51793
|
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: ecclesiastical reform law Context triple: [Rivadavia Law of Ecclesiastical Reform, instanceOf, ecclesiastical reform 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.
state–church reform program
chosen
A state–church reform program is a coordinated set of policies and actions through which a government restructures its relationship with religious institutions, typically to redefine authority, finances, legal status, and social roles.
-
C.
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.
-
D.
ecclesiastical authority
Ecclesiastical authority is the recognized power and jurisdiction exercised by religious officials or institutions to govern doctrine, discipline, and practice within a faith community.
-
E.
national reform law
A national reform law is a legislative act enacted by a country’s governing body to systematically change, modernize, or improve existing legal, social, economic, or political structures at the national level.
- 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_69f224a92f54819095499b4d32bd5134 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:33 p.m.