Triple
T27984945
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maronite Church (ecclesiastical governance) |
E706718
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sui iuris church governance |
C4016
|
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: sui iuris church governance Context triple: [Maronite Church (ecclesiastical governance), instanceOf, sui iuris church governance]
-
A.
sui iuris churches
chosen
Sui iuris churches are autonomous particular churches within the Catholic Church that govern themselves according to their own traditions and laws while remaining in full communion with the Pope.
-
B.
ecclesiastical jurisdiction
An ecclesiastical jurisdiction is a defined territorial or personal area of authority within a religious organization, governed by church law and overseen by designated clerical leaders.
-
C.
governing body of a sui iuris Eastern Catholic Church
The governing body of a sui iuris Eastern Catholic Church is the highest ecclesiastical authority within that particular Church, responsible for its internal governance, discipline, liturgy, and pastoral mission in communion with the Pope.
-
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.
internal law of a religious institute
The internal law of a religious institute is the body of norms, rules, and customs established by the institute itself to govern its members’ life, organization, discipline, and mission in harmony with the broader law of the Church.
- 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_69ef96b8b8d88190bad5e4ae966bf14e |
completed | April 27, 2026, 5:02 p.m. |
Created at: April 27, 2026, 7:47 p.m.