Triple
T10652679
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African politics |
E251009
|
entity |
| Predicate | votingSystemLevel |
P14614
|
FINISHED |
| Object | national elections |
—
|
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: national elections | Statement: [South African politics, votingSystemLevel, national elections]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: votingSystemLevel Context triple: [South African politics, votingSystemLevel, national elections]
-
A.
typeOfVoting
Indicates the specific method or system by which a vote is cast or recorded in a decision-making process.
-
B.
votingControl
Indicates that one entity has the power to determine or significantly influence the outcome of decisions made by another entity through its voting rights.
-
C.
electionSystemFeature
chosen
Indicates that an election system possesses a specific characteristic, mechanism, or procedural feature related to how elections are conducted or managed.
-
D.
votingIs
Indicates that an entity is engaged in, characterized by, or involved in the act or process of voting.
-
E.
votingBasis
Indicates the principle, criterion, or grounds on which a vote or voting decision is made.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dff78ec88190a4d1863fe87245f6 |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd8753108190b799ffa0c760526e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.