Triple
T29659822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2017 Kenyan presidential election |
E750374
|
entity |
| Predicate | initialResultAnnulmentDate |
P109451
|
FINISHED |
| Object | 2017-09-01 |
—
|
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: 2017-09-01 | Statement: [2017 Kenyan presidential election, initialResultAnnulmentDate, 2017-09-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: initialResultAnnulmentDate Context triple: [2017 Kenyan presidential election, initialResultAnnulmentDate, 2017-09-01]
-
A.
annulmentDate
chosen
Indicates the date on which a previously established relationship, agreement, or status is formally declared null and void.
-
B.
dismissalDate
Indicates the date on which an entity (such as a person, case, or employment) is formally dismissed, terminated, or ended.
-
C.
dateRescinded
Indicates that a previously established date or agreement has been officially withdrawn, canceled, or revoked.
-
D.
adjournmentDate
Indicates the date on which a meeting, session, or proceeding is formally suspended or brought to a close.
-
E.
ceaseToExistDecisionDate
Indicates the date on which a formal decision was made that something will cease to exist or be terminated.
- 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_69f0d6226fe881908819197c9ef9ee04 |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
Created at: April 28, 2026, 6:57 p.m.