Triple
T16400266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradhan Mantri Jan Dhan Yojana |
E398292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial inclusion scheme |
C30516
|
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: financial inclusion scheme Context triple: [Pradhan Mantri Jan Dhan Yojana, instanceOf, financial inclusion scheme]
-
A.
advocate for financial inclusion
An advocate for financial inclusion is an individual or organization that actively works to ensure equitable access to affordable, appropriate financial services for underserved and marginalized populations.
-
B.
direct income support scheme
A direct income support scheme is a policy mechanism through which governments or institutions provide regular, targeted cash transfers to individuals or households to stabilize income, reduce poverty, and support basic living standards.
-
C.
financing platform
A financing platform is a digital system that connects capital providers with individuals or businesses seeking funding, streamlining the processes of application, evaluation, and transaction management.
-
D.
financial initiative
A financial initiative is a planned set of actions or programs designed to allocate, manage, or invest financial resources to achieve specific economic, strategic, or social objectives.
-
E.
government-backed scheme
chosen
A government-backed scheme is a program or initiative supported, funded, or guaranteed by a governmental authority to achieve specific public policy objectives, such as economic stability, social welfare, or infrastructure development.
- 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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:09 a.m.