Triple
T33643717
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pradhan Mantri Fasal Bima Yojana |
E861899
|
entity |
| Predicate | claimSettlementMethod |
P41183
|
FINISHED |
| Object | area yield index |
—
|
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: area yield index | Statement: [Pradhan Mantri Fasal Bima Yojana, claimSettlementMethod, area yield index]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: claimSettlementMethod Context triple: [Pradhan Mantri Fasal Bima Yojana, claimSettlementMethod, area yield index]
-
A.
methodOfSettlement
Indicates the way in which a transaction, obligation, or dispute is resolved, completed, or paid.
-
B.
claimMethod
chosen
Indicates the method or procedure by which a claim is made, submitted, or executed.
-
C.
settlementMode
Indicates the method or process by which a financial or transactional obligation is settled or completed between parties.
-
D.
settlementWith
Indicates a relationship where one party reaches or maintains a settlement or agreement with another party, typically resolving a dispute or claim.
-
E.
settlementType
Indicates the specific kind or category of human settlement an entity represents, such as a city, village, town, or hamlet.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 1, 2026, 1:42 a.m.