Triple
T16400296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradhan Mantri Jan Dhan Yojana |
E398292
|
entity |
| Predicate | overdraftLimit |
P123279
|
FINISHED |
| Object | ₹5,000 (initial design) |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: ₹5,000 (initial design) | Statement: [Pradhan Mantri Jan Dhan Yojana, overdraftLimit, ₹5,000 (initial design)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overdraftLimit Context triple: [Pradhan Mantri Jan Dhan Yojana, overdraftLimit, ₹5,000 (initial design)]
-
A.
deficitLimit
Indicates a constraint or maximum allowable amount on how large a deficit (shortfall or negative balance) may be.
-
B.
oversLimit
Indicates that an entity exceeds a specified limit, threshold, or allowed maximum.
-
C.
hasMaximumBalanceLimit
Indicates that there is an upper bound on the balance that an account or entity is allowed to hold.
-
D.
guaranteeLimitBasis
Indicates the basis or criteria used to determine the limit of a guarantee in a contractual or financial context.
-
E.
amendedLimit
Indicates that a previously established limit has been modified or updated from its original value.
- F. None of above. chosen
Provenance (4 batches)
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. |
| NER | Named-entity recognition | batch_69e327cea4e481908400b852a5a7032a |
completed | April 18, 2026, 6:42 a.m. |
| PD | Predicate disambiguation | batch_69e226fe1dd08190865c181721f8c348 |
completed | April 17, 2026, 12:26 p.m. |
| PDg | Predicate description generation | batch_69e24555bb6c8190977cf5c5f9149056 |
completed | April 17, 2026, 2:36 p.m. |
Created at: April 10, 2026, 5:09 a.m.