Triple
T5806073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saint John of Rila |
E128746
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Bulgarian saint |
C16266
|
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: Bulgarian saint Context triple: [Saint John of Rila, instanceOf, Bulgarian saint]
-
A.
Georgian Orthodox saint
A Georgian Orthodox saint is a holy person recognized by the Georgian Orthodox Church for their exemplary faith, virtuous life, and often martyrdom, and is venerated as an intercessor and model of Christian living.
-
B.
Orthodox saint
chosen
An Orthodox saint is a person recognized by the Eastern Orthodox Church as having lived a life of exceptional holiness and faithfulness to God, serving as an intercessor and example for believers.
-
C.
Byzantine missionary
A Byzantine missionary is a religious emissary from the Byzantine Empire who travels to foreign regions to spread Eastern Orthodox Christianity, often serving as both a spiritual teacher and cultural ambassador.
-
D.
Serbian Orthodox priest
A Serbian Orthodox priest is a Christian cleric ordained in the Serbian Orthodox Church who leads liturgical services, administers sacraments, offers spiritual guidance, and upholds the traditions and teachings of Eastern Orthodoxy within the Serbian cultural and religious context.
-
E.
Apostle to the Slavs
Apostle to the Slavs is a conceptual class representing a missionary figure devoted to evangelizing Slavic peoples, translating sacred texts into their languages, and shaping their religious and cultural identity.
- 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_69c00846a0d881909e46841f8e156b64 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:52 p.m.