Triple
T2927246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kraljevo (Žiča) |
E78874
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian Orthodox religious site |
C2511
|
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: Serbian Orthodox religious site Context triple: [Kraljevo (Žiča), instanceOf, Serbian Orthodox religious site]
-
A.
Eastern Orthodox church
An Eastern Orthodox church is a Christian place of worship characterized by its adherence to Eastern Orthodox theology and liturgy, often featuring domes, icons, and a richly decorated interior focused on the Divine Liturgy.
-
B.
Eastern Orthodox Christian
An Eastern Orthodox Christian is a follower of the Eastern Orthodox Church who adheres to its ancient liturgical traditions, theology, and spiritual practices centered on the Holy Trinity, the sacraments, and the continuity of the early Christian faith.
-
C.
religious site
chosen
A religious site is a designated place or structure where individuals or communities engage in worship, rituals, and other practices associated with their faith or spiritual beliefs.
-
D.
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.
-
E.
Eastern Orthodox monastery
An Eastern Orthodox monastery is a religious community where monks or nuns live a communal life of prayer, worship, asceticism, and service according to the traditions and spiritual practices of 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_69ad8b0d40b481908bc2a5fa2e73c3fb |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 2:55 p.m.