Triple
T30229805
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kenyan general elections |
E768594
|
entity |
| Predicate | reformDriver |
P169002
|
FINISHED |
| Object | 2007–2008 post-election crisis |
—
|
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: 2007–2008 post-election crisis | Statement: [Kenyan general elections, reformDriver, 2007–2008 post-election crisis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reformDriver Context triple: [Kenyan general elections, reformDriver, 2007–2008 post-election crisis]
-
A.
reformerOf
Indicates that one entity is the person or agent who initiated or carried out significant reforms or changes to another entity.
-
B.
reformsBy
Indicates that one entity initiates, implements, or is responsible for changes or improvements (reforms) affecting another entity.
-
C.
reform
Indicates bringing about significant changes to an existing system, practice, or entity in order to improve or correct it.
-
D.
reformName
Indicates that an entity has undergone a reform or change resulting in a new name or designation.
-
E.
subjectToReformBy
Indicates that an entity is undergoing or designated for changes, improvements, or restructuring carried out by another entity.
- F. None of above. chosen
Provenance (4 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_69f2248108208190be60bf1af343ce70 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6802486ac8190a936df82f2988383 |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 29, 2026, 7:36 p.m.