Triple
T19071762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rishama |
E466808
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Mandaean religious office |
C41139
|
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: Mandaean religious office Context triple: [Rishama, instanceOf, Mandaean religious office]
-
A.
Yazidi religious office
A Yazidi religious office is a formal spiritual role or position within the Yazidi community responsible for performing rituals, preserving sacred traditions, and providing religious leadership and guidance.
-
B.
Yazidi holy personage
A Yazidi holy personage is a revered religious figure within the Yazidi faith, often associated with spiritual authority, guardianship of sacred traditions, and intercession between the community and the divine.
-
C.
Mandaean diaspora
The Mandaean diaspora refers to the global dispersion of the Mandaean religious and ethnic community from their historic homelands in Iraq and Iran, resulting in scattered communities striving to preserve their distinct Gnostic traditions, language, and rituals in new cultural contexts.
-
D.
Mandaean legal-theological text
A Mandaean legal-theological text is a written work that codifies religious laws, rituals, and doctrinal teachings within the Mandaean faith, guiding both communal practice and spiritual belief.
-
E.
Mandaean cosmological text
A Mandaean cosmological text is a religious work of the Mandaean tradition that describes the structure, origins, and metaphysical realms of the universe, including the relationships between the World of Light, the material world, and the soul’s journey.
- F. None of above. chosen
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_69d8dd04f4488190b1121cc53ef2bfd6 |
completed | April 10, 2026, 11:20 a.m. |
Created at: April 10, 2026, 12:04 p.m.