Triple
T3188158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Orthodox Church Outside Russia |
E66752
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | autonomous 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: autonomous ecclesiastical jurisdiction Context triple: [Russian Orthodox Church Outside Russia, instanceOf, autonomous 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.
autocephalous Eastern Orthodox church
An autocephalous Eastern Orthodox church is a self-governing ecclesiastical body within Eastern Orthodoxy whose highest bishop does not report to any higher-ranking bishop and independently manages its internal affairs while remaining in communion with other Orthodox churches.
-
C.
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.
-
D.
sui iuris churches
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.
-
E.
group of dioceses
A group of dioceses is an ecclesiastical jurisdiction composed of multiple dioceses united under a higher church authority, such as a province or patriarchate.
- 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_69ad8587c1bc8190a2595f2c22ee1001 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:06 p.m.