Triple
T5738763
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aspirational Districts Programme |
E126561
|
entity |
| Predicate | usesIncentives |
P7916
|
FINISHED |
| Object | performance-based incentives for districts |
—
|
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: performance-based incentives for districts | Statement: [Aspirational Districts Programme, usesIncentives, performance-based incentives for districts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesIncentives Context triple: [Aspirational Districts Programme, usesIncentives, performance-based incentives for districts]
-
A.
typeOfIncentive
chosen
Indicates the specific kind or category of incentive associated with an entity or action.
-
B.
ownerIncentive
Indicates that an owner has a motivation, benefit, or reward associated with a particular entity, action, or outcome.
-
C.
eligibleUses
Indicates the types of actions, purposes, or contexts in which something is permitted or qualified to be used.
-
D.
rewardUse
Indicates that one entity grants or provides a reward in response to the use or utilization of another entity.
-
E.
loyaltyIncentive
Indicates a relationship where benefits or rewards are provided to encourage or recognize continued commitment or repeat engagement.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255dc35c8190ab9ee5d269ce553a |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:48 p.m.