Triple
T26508694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beas Project |
E669620
|
entity |
| Predicate | stateBeneficiary |
P59816
|
FINISHED |
| Object | Punjab |
—
|
NE NERFINISHED |
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: Punjab | Statement: [Beas Project, stateBeneficiary, Punjab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stateBeneficiary Context triple: [Beas Project, stateBeneficiary, Punjab]
-
A.
beneficiaryStates
chosen
Indicates that certain states receive benefits, advantages, or positive outcomes from a particular action, event, or arrangement.
-
B.
beneficiaryBody
Indicates that one entity serves as the benefiting body or organization that receives advantage, support, or services from another entity or action.
-
C.
beneficiaryRegion
Indicates the region that receives the benefit, advantage, or positive impact resulting from an action, resource, or arrangement.
-
D.
beneficiaryCountry
Indicates that one country is the recipient or beneficiary of aid, resources, or advantages provided in a given context.
-
E.
beneficiaryRole
Indicates that one entity serves as the beneficiary or recipient of an action, service, or resource provided by another entity.
- 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_69eeb319ec70819090834c2591cf5f1e |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f6db1f3ec48190a82e7d893d3c76ba |
completed | May 3, 2026, 5:20 a.m. |
| PD | Predicate disambiguation | batch_69f6d82adfa481908a5e196d2e18c73f |
completed | May 3, 2026, 5:07 a.m. |
Created at: April 27, 2026, 1:18 a.m.