Triple
T18970337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zanzibar and Pemba People’s Party |
E464148
|
entity |
| Predicate | resultOfRevolution |
P61484
|
FINISHED |
| Object | loss of political power |
—
|
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: loss of political power | Statement: [Zanzibar and Pemba People’s Party, resultOfRevolution, loss of political power]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultOfRevolution Context triple: [Zanzibar and Pemba People’s Party, resultOfRevolution, loss of political power]
-
A.
postRevolution
chosen
Indicates that one event, condition, or state occurs or exists after a revolution has taken place.
-
B.
resultOfUprising
Indicates that something exists or occurs as a consequence or outcome of an uprising or rebellion.
-
C.
revolutionVictoryYear
Indicates the year in which a revolution achieved victory or successfully overthrew the existing regime.
-
D.
overthrewGovernment
Indicates that an entity forcibly removed an existing government from power, typically replacing it with a new regime.
-
E.
revolutionaryBody
Indicates a body or organization that leads, governs, or coordinates a revolutionary movement or uprising.
- 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_69d8dd008af48190a97ff1c6488edf1b |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d619acbc8190acb49b3fae707758 |
completed | April 20, 2026, 7:30 a.m. |
| PD | Predicate disambiguation | batch_69e4a2f437648190b85650dae8885d48 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, noon