Triple
T5940307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soweto Uprising |
E132149
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in the apartheid era |
C11176
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: event in the apartheid era Context triple: [Soweto Uprising, instanceOf, event in the apartheid era]
-
A.
event in South African history
chosen
An event in South African history is a significant occurrence or series of actions within South Africa’s past that influenced its political, social, economic, or cultural development.
-
B.
event in the Civil Rights Movement
An event in the Civil Rights Movement is a historically specific occurrence—such as a protest, march, court decision, or legislative action—that contributed to the struggle against racial segregation and discrimination in the United States.
-
C.
anti-apartheid film
An anti-apartheid film is a motion picture that portrays, critiques, and raises awareness about South Africa’s apartheid system, highlighting its injustices and often advocating for social and political change.
-
D.
anti-apartheid activist
An anti-apartheid activist is an individual who actively opposes and works to dismantle systems of racial segregation, discrimination, and oppression, particularly those modeled on or inspired by South Africa’s former apartheid regime.
-
E.
event in Nazi Germany
An event in Nazi Germany is a historically situated occurrence—political, social, military, cultural, or economic—that took place under the National Socialist regime between 1933 and 1945 and contributed to its policies, ideology, or consequences.
- F. None of above.
Provenance (1 batch)
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_69c0085c55dc8190aa90e242c956e2fa |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 4:01 p.m.