Triple
T27742241
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 South African general election |
E701884
|
entity |
| Predicate | spoiltVotes |
P63379
|
FINISHED |
| Object | 251960 |
—
|
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: 251960 | Statement: [2014 South African general election, spoiltVotes, 251960]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spoiltVotes Context triple: [2014 South African general election, spoiltVotes, 251960]
-
A.
voted
Indicates that an entity formally expressed a choice or decision, typically in an election, poll, or decision-making process, regarding another entity or option.
-
B.
invalidatedVotesShare
Indicates the proportion of all cast votes that were declared invalid or void.
-
C.
votesOnly
Indicates that an entity participates in a decision-making process solely by casting votes, without engaging in any other associated actions or roles.
-
D.
spoilsDisposition
Indicates that one entity negatively alters, ruins, or undermines the intended state, condition, or arrangement of another entity.
-
E.
voteCount
chosen
Indicates the number of votes that have been cast for or associated with a particular item or option.
- 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_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. |
Created at: April 27, 2026, 4:12 p.m.