Triple
T19897379
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Janata Dal (Secular) |
E478184
|
entity |
| Predicate | opposesPolicyArea |
P33291
|
FINISHED |
| Object | centralisation of power |
—
|
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: centralisation of power | Statement: [Janata Dal (Secular), opposesPolicyArea, centralisation of power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opposesPolicyArea Context triple: [Janata Dal (Secular), opposesPolicyArea, centralisation of power]
-
A.
opposedPolicyContext
Indicates that an entity opposed a specific policy within a particular situational, temporal, or institutional context.
-
B.
opposesLabel
Indicates that one entity expresses disagreement with, resistance to, or active opposition against another entity or its position.
-
C.
advocatesAgainst
chosen
Indicates that one entity actively opposes, argues against, or campaigns to prevent or stop another entity, action, or idea.
-
D.
commonPolicyArea
Indicates that two entities share the same policy domain, topic, or area of regulatory or legislative focus.
-
E.
supportsPolicyArea
Indicates that one entity endorses, advocates for, or is in favor of a particular policy area or domain of public policy.
- 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e6593ef8dc8190be5b64988eceafac |
completed | April 20, 2026, 4:50 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:52 p.m.