Triple
T28025651
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2019 South African general election |
E708115
|
entity |
| Predicate | tookPlace |
P120568
|
FINISHED |
| Object | 25 years after the end of apartheid |
—
|
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: 25 years after the end of apartheid | Statement: [2019 South African general election, tookPlace, 25 years after the end of apartheid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tookPlace Context triple: [2019 South African general election, tookPlace, 25 years after the end of apartheid]
-
A.
takesPlace
chosen
Indicates that an event or action occurs or is situated at a particular time, place, or context.
-
B.
tookPlaceFrom
Indicates that an event or occurrence started or was ongoing beginning at a specified time or location.
-
C.
tookPlaceAtEvent
Indicates that an action or occurrence happened during or in the context of a specific event.
-
D.
tookPlaceInCategory
Indicates that an event or occurrence happened within, or is classified under, a particular category.
-
E.
tookPlaceInAdministrativeEntity
Indicates that an event or occurrence happened within the jurisdiction or boundaries of a specific administrative entity.
- 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_69ef9b6bdd9c8190bb3a574a03774ad1 |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f63fd79e4c8190af9263b679e5ff07 |
completed | May 2, 2026, 6:17 p.m. |
| PD | Predicate disambiguation | batch_69f63c6a8474819091b8c6fe98e3862d |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 8:12 p.m.