Triple
T10593587
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwean presidential election, 2002 |
E250052
|
entity |
| Predicate | resultAcceptedByGovernment |
P94822
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Zimbabwean presidential election, 2002, resultAcceptedByGovernment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resultAcceptedByGovernment Context triple: [Zimbabwean presidential election, 2002, resultAcceptedByGovernment, true]
-
A.
succeededByGovernment
Indicates that one government is directly followed and replaced in power or authority by another government.
-
B.
supportedGovernment
Indicates that one entity provided assistance, endorsement, or backing to a particular government or governing authority.
-
C.
resultedInGovernmentNumber
Indicates that one event, action, or condition caused or produced a specific government-issued identification number.
-
D.
governmentOutcome
Indicates the result, consequence, or effect produced by a government’s decisions, actions, or policies.
-
E.
implementedGovernmentType
Indicates the specific form of government that has been put into practice or adopted by an 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_69d381c9d3d48190a29ee491e1696a0e |
completed | April 6, 2026, 9:50 a.m. |
| NER | Named-entity recognition | batch_69d5277da8048190add007ca0c37253e |
completed | April 7, 2026, 3:49 p.m. |
| PD | Predicate disambiguation | batch_69d51907b2b881908ab9a8594688ee06 |
completed | April 7, 2026, 2:47 p.m. |
| PDg | Predicate description generation | batch_69d5270eca0481908573b698390c5b08 |
completed | April 7, 2026, 3:47 p.m. |
Created at: April 6, 2026, 12:40 p.m.