Triple
T32134829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Madhes movements of 2007 |
E820740
|
entity |
| Predicate | demandedChangeIn |
P94743
|
FINISHED |
| Object | electoral system of Nepal |
—
|
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: electoral system of Nepal | Statement: [Madhes movements of 2007, demandedChangeIn, electoral system of Nepal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: demandedChangeIn Context triple: [Madhes movements of 2007, demandedChangeIn, electoral system of Nepal]
-
A.
demanded
Indicates that one entity forcefully or insistently requested something from another entity.
-
B.
changesRequirement
Indicates that one entity modifies, updates, or alters the requirements associated with another entity.
-
C.
demandedReformFrom
chosen
Indicates that one party insisted that another party implement or agree to specific changes or reforms.
-
D.
changeRequestsImplementedBy
Indicates that the specified change requests have been carried out or fulfilled by the referenced implementing entity.
-
E.
demandedConcessionTo
Indicates that one party insisted another party grant a concession, typically as a condition or requirement in a negotiation or conflict.
- 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_69f349039e0c819091c7a7d322e3f46d |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b3a970b0819090c6473844ffa8e3 |
completed | May 3, 2026, 2:32 a.m. |
Created at: May 1, 2026, 12:30 a.m.