Triple
T29659890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jubilee Alliance |
E750375
|
entity |
| Predicate | announcedMergerInto |
P121113
|
FINISHED |
| Object | Jubilee Party of Kenya |
—
|
NE NERFINISHED |
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: Jubilee Party of Kenya | Statement: [Jubilee Alliance, announcedMergerInto, Jubilee Party of Kenya]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedMergerInto Context triple: [Jubilee Alliance, announcedMergerInto, Jubilee Party of Kenya]
-
A.
mergerAnnounced
chosen
Indicates that an official announcement has been made that two or more entities intend to merge into a single combined entity.
-
B.
demergedInto
Indicates that an entity has been split or separated into one or more distinct successor entities as a result of a demerger process.
-
C.
agreedToMerger
Indicates that two or more parties have formally consented to combine their organizations or assets into a single merged entity.
-
D.
mergerResultedIn
Indicates that a merger between entities led to the creation, change, or outcome represented by the related entity or state.
-
E.
wasRestructuredInto
Indicates that an entity underwent an organizational or structural change resulting in it becoming a different, successor entity.
- 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_69f671bf54688190a920fed1847a1a9b |
completed | May 2, 2026, 9:50 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 6:57 p.m.