Triple
T4823597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sangh Parivar |
E107767
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Hindu nationalist movement |
C16441
|
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: Hindu nationalist movement Context triple: [Sangh Parivar, instanceOf, Hindu nationalist movement]
-
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.
Hindu extremist
A Hindu extremist is an individual or group that adopts radical, intolerant, and often violent interpretations of Hindu identity or ideology to justify hostility or aggression toward perceived religious, cultural, or political opponents.
-
C.
Indian nationalist
An Indian nationalist is an individual who strongly identifies with and advocates for the unity, sovereignty, cultural heritage, and political interests of India as a nation.
-
D.
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.
-
E.
Indian independence movement organization
An Indian independence movement organization is a group formed to plan, coordinate, and execute political, social, or revolutionary activities aimed at ending British colonial rule and achieving self-governance for India.
- 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_69bd43f9efa081908314cb3e94fa1695 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:24 p.m.