Triple
T18003692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bishopric of Michoacán |
E430689
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | colonial 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: colonial ecclesiastical jurisdiction Context triple: [Bishopric of Michoacán, instanceOf, colonial 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 state
An ecclesiastical state is a political entity in which the government is directly controlled by religious authorities, often with a church leader serving as the head of state.
-
C.
ecclesiastical court system
An ecclesiastical court system is a hierarchical network of church-run tribunals that adjudicate matters of doctrine, discipline, and religious law within a particular faith community.
-
D.
missionary diocese
A missionary diocese is a territorial ecclesiastical jurisdiction, often in a developing or non-traditional Christian region, established to organize and advance the church’s missionary, pastoral, and evangelizing work under the authority of a bishop or equivalent leader.
-
E.
Ethiopian Catholic jurisdiction
An Ethiopian Catholic jurisdiction is an ecclesiastical territory of the Ethiopian Catholic Church, led by a bishop or eparch, responsible for overseeing the pastoral care, administration, and liturgical life of Ethiopian Catholics within a defined geographic area.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
Created at: April 10, 2026, 10:23 a.m.