Triple
T29659859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee Alliance |
E750375
|
entity |
| Predicate | formedForOffice |
P197411
|
FINISHED |
| Object | President of Kenya |
—
|
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: President of Kenya | Statement: [Jubilee Alliance, formedForOffice, President of Kenya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formedForOffice Context triple: [Jubilee Alliance, formedForOffice, President of Kenya]
-
A.
formedForElection
chosen
Indicates that an organization, group, or entity was created specifically for the purpose of participating in or supporting a particular election.
-
B.
composedOfOffice
Indicates that something is made up of, or structurally includes, one or more offices as its constituent parts.
-
C.
formerOfficialIn
Indicates that an entity once held an official position or office within another entity but no longer does.
-
D.
officeFormation
Indicates the event or process by which an office or official position is created, established, or formally constituted.
-
E.
nominatesForOffice
Indicates that one entity formally proposes or selects another entity as a candidate to hold a particular office or position.
- 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_69fe920a437081908d5174e8cf7a53a6 |
completed | May 9, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69fe919a9a6c8190acb4483f386e6db7 |
completed | May 9, 2026, 1:44 a.m. |
Created at: April 28, 2026, 6:57 p.m.