Triple
T38043161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gopal Hari Deshmukh |
E949544
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Maharashtrian social reformer |
C29347
|
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: Maharashtrian social reformer Context triple: [Gopal Hari Deshmukh, instanceOf, Maharashtrian social reformer]
-
A.
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.
-
B.
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.
-
C.
Indian social worker
chosen
An Indian social worker is a professional or volunteer dedicated to improving the welfare, rights, and living conditions of individuals and communities in India through advocacy, support services, and social development programs.
-
D.
Parsi political leader
A Parsi political leader is a public figure of Zoroastrian Parsi heritage who actively participates in governance, policy-making, or political advocacy, representing both broader civic interests and, at times, the concerns of the Parsi community.
-
E.
key figure of the Bengal Renaissance
A key figure of the Bengal Renaissance is an influential individual whose intellectual, cultural, social, or political contributions significantly shaped the 19th–early 20th century movement for modernity, reform, and artistic flourishing in Bengal.
- 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_69f76eff0bb0819084bc4e63997bd039 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.