Triple
T28398419
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Islamization of Persia |
E719340
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | socio‑religious phenomenon |
C14352
|
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: socio‑religious phenomenon Context triple: [Islamization of Persia, instanceOf, socio‑religious phenomenon]
-
A.
religious phenomenon
chosen
A religious phenomenon is any observable event, practice, experience, or pattern of belief that arises within or in relation to a religious tradition, worldview, or sense of the sacred.
-
B.
modern religious movement
A modern religious movement is a contemporary, organized system of spiritual beliefs and practices that has emerged relatively recently, often in response to social, cultural, or technological changes, and may reinterpret or break from established religious traditions.
-
C.
humanist religious movement
A humanist religious movement is a faith-oriented community or tradition that centers human dignity, reason, and ethical responsibility while often reinterpreting or minimizing supernatural beliefs.
-
D.
medieval religious movement
A medieval religious movement is a collective effort during the Middle Ages to reform, renew, or challenge existing religious beliefs and institutions, often blending spiritual, social, and political aims.
-
E.
religious conversion movement
A religious conversion movement is a collective effort or organized campaign aimed at persuading individuals or groups to adopt a new religious faith, denomination, or set of spiritual beliefs, often involving structured teachings, rituals, and community support.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:18 a.m.