Triple
T15684062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stefan Nemanja |
E380150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Serbian Orthodox monk |
C24262
|
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 monk Context triple: [Stefan Nemanja, instanceOf, Serbian Orthodox monk]
-
A.
Eastern Orthodox monk
chosen
An Eastern Orthodox monk is a man who has taken religious vows within the Eastern Orthodox Church, dedicating his life to prayer, asceticism, communal or solitary monastic living, and the pursuit of spiritual union with God.
-
B.
Syriac Christian monk
A Syriac Christian monk is a member of an ascetic religious community within the Syriac Christian tradition, devoted to prayer, contemplation, and communal or solitary monastic life shaped by Syriac liturgy, language, and theology.
-
C.
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.
-
D.
Catholic monk
A Catholic monk is a man who has taken religious vows within the Catholic Church and lives in a community or cloister dedicated to prayer, work, and spiritual discipline.
-
E.
Orthodox saint
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.
- 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_69d86d99e860819094b6957cde470f2c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:43 a.m.