Triple
T22681299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Archbishopric of Belgrade and Karlovci |
E560488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | eparchy of the Serbian Orthodox Church |
C34038
|
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: eparchy of the Serbian Orthodox Church Context triple: [Archbishopric of Belgrade and Karlovci, instanceOf, eparchy of the Serbian Orthodox Church]
-
A.
organ of the Serbian Orthodox Church
An organ of the Serbian Orthodox Church is an official institutional body or administrative unit that performs specific religious, governance, or organizational functions within the Church’s hierarchical structure.
-
B.
Serbian Orthodox Patriarch
The Serbian Orthodox Patriarch is the supreme spiritual leader and highest-ranking bishop of the Serbian Orthodox Church, responsible for guiding its doctrine, liturgy, and administration.
-
C.
Metropolitan archeparchy
chosen
A metropolitan archeparchy is a principal Eastern Catholic ecclesiastical jurisdiction, headed by a metropolitan archbishop, that presides over its own territory and often has suffragan eparchies under its authority.
-
D.
Ukrainian Greek Catholic archeparchy
A Ukrainian Greek Catholic archeparchy is a principal ecclesiastical jurisdiction of the Ukrainian Greek Catholic Church, headed by an archeparch and overseeing multiple eparchies within a defined territory.
-
E.
organ of the Bulgarian Orthodox Church
An organ of the Bulgarian Orthodox Church is an official institutional body or administrative unit that performs specific religious, governance, or support functions within the Church’s hierarchical structure.
- 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_69e2454bfd00819099115715a22cb057 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:12 p.m.