Triple
T15704236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Temple Entry Proclamation of 1936 |
E380666
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | anti-untouchability reform |
C11934
|
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: anti-untouchability reform Context triple: [Temple Entry Proclamation of 1936, instanceOf, anti-untouchability reform]
-
A.
Hindu reform movement
chosen
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.
legal reform
Legal reform is the process of reviewing, amending, and modernizing laws and legal institutions to better reflect current societal values, address injustices, and improve the effectiveness of the legal system.
-
D.
social reform proposal
A social reform proposal is a structured plan or recommendation aimed at changing existing social policies, institutions, or practices to address perceived injustices or improve societal well-being.
-
E.
sexual reform movement
The sexual reform movement is a social and political campaign aimed at challenging and changing traditional norms, laws, and attitudes surrounding sexuality, gender roles, and reproductive rights to promote greater freedom, equality, and bodily autonomy.
- 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_69d86d9bf930819082b30cf6d169297c |
completed | April 10, 2026, 3:25 a.m. |
Created at: April 10, 2026, 4:45 a.m.