Triple
T27742250
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 South African general election |
E701884
|
entity |
| Predicate | DAVoteSharePercentage |
P163182
|
FINISHED |
| Object | 22.23 |
—
|
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: 22.23 | Statement: [2014 South African general election, DAVoteSharePercentage, 22.23]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: DAVoteSharePercentage Context triple: [2014 South African general election, DAVoteSharePercentage, 22.23]
-
A.
DVPVoteShare
Indicates the proportion of total votes that were cast for the DVP party in an election.
-
B.
hasVotingPowerPerShare
Indicates that an entity possesses a specified amount of voting power associated with each individual share it holds.
-
C.
hasVotingStake
Indicates that one entity possesses a share of voting power or decision-making authority in another entity.
-
D.
publicVoteWeight
Indicates that an entity’s influence or impact in a public voting process is quantified by a specific weight or value.
-
E.
psoeVoteShare
Indicates the proportion of total votes received by the PSOE party in an election or voting context.
- 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63717b8c48190abd8ebcc54c76c46 |
completed | May 2, 2026, 5:40 p.m. |
| PD | Predicate disambiguation | batch_69f63188e7408190af8ce8b93d128c63 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6352df6148190bc10772cd40bd7b3 |
completed | May 2, 2026, 5:32 p.m. |
Created at: April 27, 2026, 4:12 p.m.