Triple
T22005032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atmiya Sabha |
E543429
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | socio-religious reform association |
C12390
|
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 reform association Context triple: [Atmiya Sabha, instanceOf, socio-religious reform association]
-
A.
Hindu reform movement
A Hindu reform movement is a religious and social initiative within Hinduism that seeks to reinterpret traditional beliefs and practices in light of modern values such as rationalism, social equality, and individual rights.
-
B.
Sikh reform movement
The Sikh reform movement refers to a series of religious, social, and political efforts—especially from the late 19th century onward—to purify Sikh practices, revive core Sikh doctrines, and assert Sikh identity distinct from Hindu and colonial influences.
-
C.
Arya Samaj leader
An Arya Samaj leader is a prominent figure who guides and promotes the reformist, Vedic-based principles of the Arya Samaj movement through religious, social, and educational activities.
-
D.
Hindu religious reformer
A Hindu religious reformer is an individual who seeks to reinterpret, purify, and revitalize Hindu beliefs and practices in response to social, moral, or spiritual concerns of their time.
-
E.
religious social reform group
chosen
A religious social reform group is an organized collective that, motivated by shared faith-based values, seeks to transform social structures, norms, and policies to promote moral, ethical, and humanitarian change.
- 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_69e11e2db934819095556760c7d85e4d |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:20 p.m.