Triple
T860395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tolstoyanism |
E18586
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | religious philosophical movement |
C534
|
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: religious philosophical movement Context triple: [Tolstoyanism, instanceOf, religious philosophical movement]
-
A.
philosophical movement
chosen
A philosophical movement is a historically and intellectually coherent trend in philosophy, characterized by shared themes, methods, and assumptions among a group of thinkers over a particular period or context.
-
B.
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.
-
C.
religious belief
Religious belief is a deeply held conviction or faith in spiritual principles, deities, or transcendent realities that shapes an individual's understanding of existence, morality, and purpose.
-
D.
religious tradition
A religious tradition is an enduring, socially shared system of beliefs, practices, narratives, and institutions that shapes how a community understands and relates to the sacred, the moral order, and ultimate meaning.
-
E.
Jewish religious movement
A Jewish religious movement is an organized stream within Judaism that shares distinctive beliefs, practices, and interpretations of Jewish law and tradition, shaping how its adherents understand and live out Jewish 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_69a4938bdd3c8190a954a3c11844d9cf |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.