Triple
T35198141
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Foros parish |
E1016324
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Orthodox parish |
C18572
|
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: Orthodox parish Context triple: [Foros parish, instanceOf, Orthodox parish]
-
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.
Orthodox Christian institution
chosen
An Orthodox Christian institution is an organized body, such as a church, monastery, or educational center, that preserves, practices, and transmits the faith, worship, and traditions of Eastern Orthodox Christianity within a structured communal framework.
-
C.
Orthodox church building
An Orthodox church building is a sacred Christian structure designed for Eastern Orthodox worship, typically featuring a domed roof, iconostasis, and richly decorated icons that facilitate liturgical rites and communal prayer.
-
D.
Byzantine Rite Church
A Byzantine Rite Church is a Christian church that follows the liturgical, theological, and spiritual traditions of the Byzantine rite, characterized by its Eastern Christian worship, iconography, and ecclesiastical customs.
-
E.
Eastern Orthodox archdiocese
An Eastern Orthodox archdiocese is a major ecclesiastical jurisdiction of the Eastern Orthodox Church, headed by an archbishop or metropolitan, overseeing multiple dioceses, parishes, and clergy within a defined geographic region.
- 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_69f76dde814c8190a71f60d514a424a4 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.