Triple
T3963200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Council of 1917–1918 |
E85953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Russian Orthodox Church council |
C14255
|
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: Russian Orthodox Church council Context triple: [Local Council of 1917–1918, instanceOf, Russian Orthodox Church council]
-
A.
Russian Orthodox church
A Russian Orthodox church is a Christian religious building belonging to the Russian Orthodox tradition, characterized by its distinctive onion domes, iconostasis, and liturgical practices rooted in Eastern Orthodoxy.
-
B.
organ of the Russian Orthodox Church
chosen
An organ of the Russian Orthodox Church is a formal institutional body or administrative unit within the Church that carries out specific religious, governance, or organizational functions under its canonical authority.
-
C.
Russian Orthodox bishop
A Russian Orthodox bishop is a high-ranking cleric in the Russian Orthodox Church responsible for overseeing dioceses, administering sacraments, guiding clergy and laity, and preserving the traditions and doctrines of Eastern Orthodoxy within his jurisdiction.
-
D.
Catholic Church council
A Catholic Church council is a formal assembly of bishops and other church leaders convened to deliberate and decide on matters of doctrine, discipline, and church governance.
-
E.
Eastern Orthodox bishop
An Eastern Orthodox bishop is a high-ranking cleric who holds apostolic succession and oversees the spiritual, liturgical, and administrative life of a diocese within the Eastern Orthodox 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_69aed93a96908190bcbdbfa718f155bd |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:31 p.m.