Triple
T33643688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradhan Mantri Fasal Bima Yojana |
E861899
|
entity |
| Predicate | coversRisk |
P110604
|
FINISHED |
| Object | natural calamities |
—
|
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: natural calamities | Statement: [Pradhan Mantri Fasal Bima Yojana, coversRisk, natural calamities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: coversRisk Context triple: [Pradhan Mantri Fasal Bima Yojana, coversRisk, natural calamities]
-
A.
riskCoverage
chosen
Indicates the extent to which a particular risk is protected against, mitigated, or compensated for by a policy, measure, or arrangement.
-
B.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
C.
riskResponse
Indicates how an entity reacts to, mitigates, or manages an identified risk.
-
D.
riskTakenFor
Indicates that one entity accepts or undertakes a risk for the benefit, protection, or sake of another entity.
-
E.
focusesOnRisk
Indicates that the subject directs attention, resources, or analysis primarily toward identifying, assessing, or managing risk.
- F. None of above.
Provenance (3 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_69f3498280c48190bcc3494017d14234 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcab6e888881908ca9e18660928a40 |
completed | May 7, 2026, 3:10 p.m. |
| PD | Predicate disambiguation | batch_69fc4562a5b88190bad48f083a6dcdfa |
completed | May 7, 2026, 7:55 a.m. |
Created at: May 1, 2026, 1:42 a.m.