Triple
T3875134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Personal Prelature of Ayaviri |
E92482
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Catholic ecclesiastical jurisdiction |
C575
|
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: Catholic ecclesiastical jurisdiction Context triple: [Personal Prelature of Ayaviri, instanceOf, Catholic ecclesiastical jurisdiction]
-
A.
ecclesiastical jurisdiction
chosen
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.
-
B.
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.
-
C.
Latin Catholic diocese
A Latin Catholic diocese is a territorial ecclesiastical jurisdiction of the Latin Church, governed by a bishop who oversees the pastoral care, administration, and spiritual life of Catholics within its boundaries.
-
D.
Roman Catholic ecclesiastical province
A Roman Catholic ecclesiastical province is a territorial grouping of dioceses under the leadership of a metropolitan archbishop, established to coordinate pastoral activity and governance within a defined region of the Church.
-
E.
office in the Catholic Church
An office in the Catholic Church is an established position of ecclesiastical responsibility, authority, or service, entrusted to a person for the governance, ministry, or administration 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_69aed967448c819086c4b358d37b25aa |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:20 p.m.