Triple
T5075883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saharias |
E114393
|
entity |
| Predicate | beneficiaryOf |
P52361
|
FINISHED |
| Object | tribal welfare schemes in India |
—
|
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: tribal welfare schemes in India | Statement: [Saharias, beneficiaryOf, tribal welfare schemes in India]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beneficiaryOf Context triple: [Saharias, beneficiaryOf, tribal welfare schemes in India]
-
A.
beneficiaryType
Indicates the type or category of beneficiary that receives or is intended to receive the benefit or outcome of an action or resource.
-
B.
beneficiaries
Indicates that certain entities receive advantages, profits, or positive outcomes from an action, event, or arrangement.
-
C.
beneficiaryRole
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
-
D.
recipientOf
chosen
Indicates that one entity is the receiver or beneficiary of something (such as an item, message, or action) from another entity.
-
E.
beneficiaryCountry
Indicates that one country is the recipient or beneficiary of aid, resources, or advantages provided in a given context.
- 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_69bd443dbf908190a9401e9c2dc7bd7d |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd74d2243481908c1ae62f7123c4e9 |
completed | March 20, 2026, 4:24 p.m. |
| PD | Predicate disambiguation | batch_69bd7157fe608190b4515d56fdd0a616 |
completed | March 20, 2026, 4:10 p.m. |
Created at: March 20, 2026, 1:39 p.m.