Triple
T25115539
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panchayati Raj |
E629116
|
entity |
| Predicate | assignsPowers |
P21124
|
FINISHED |
| Object | preparation of plans for economic development |
—
|
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: preparation of plans for economic development | Statement: [Panchayati Raj, assignsPowers, preparation of plans for economic development]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assignsPowers Context triple: [Panchayati Raj, assignsPowers, preparation of plans for economic development]
-
A.
allocatesPowersBetween
Indicates the way in which authority or decision-making powers are distributed or divided among different entities.
-
B.
grantedPower
Indicates that one entity has conferred authority, control, or a specific capability to another entity.
-
C.
typeOfPowerGranted
chosen
Indicates the specific kind or category of power or authority that is conferred from one entity to another.
-
D.
assignsRoleTo
Indicates that one entity designates or grants a specific role or position to another entity.
-
E.
assignsExecutivePowerTo
Indicates that executive authority or decision-making power is formally granted from one entity to another.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f465c66cc48190b66b14e4b9036432 |
completed | May 1, 2026, 8:35 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:27 a.m.