Triple
T10887151
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zimbabwean general election, 2018 |
E257077
|
entity |
| Predicate | registeredVoters |
P31216
|
FINISHED |
| Object | approximately 5.7 million |
—
|
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: approximately 5.7 million | Statement: [Zimbabwean general election, 2018, registeredVoters, approximately 5.7 million]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: registeredVoters Context triple: [Zimbabwean general election, 2018, registeredVoters, approximately 5.7 million]
-
A.
eligibleVoters
Indicates that the referenced entities are legally permitted and qualified to vote in a given election or jurisdiction.
-
B.
voterRegistration
chosen
Indicates that an entity is formally registered and eligible to vote within a particular jurisdiction or electoral system.
-
C.
numberOfVoters
Indicates the total count of individuals who participated in a particular vote or election.
-
D.
hasVoterRegister
Indicates that an entity maintains or possesses an official register or list of eligible voters.
-
E.
requiredVoterRegistration
Indicates that an entity must be registered as a voter in order to participate in a specified voting-related activity or process.
- 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_69d6aa848804819081b2713ca0bedf06 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d75201e6888190a2bc41a17784eec3 |
completed | April 9, 2026, 7:15 a.m. |
| PD | Predicate disambiguation | batch_69d70d3943c881908895397eccc3e415 |
completed | April 9, 2026, 2:21 a.m. |
Created at: April 8, 2026, 9:21 p.m.