Triple
T34199297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treason Trial (South Africa) |
E877329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | apartheid-era event |
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: apartheid-era event Context triple: [Treason Trial (South Africa), instanceOf, apartheid-era event]
-
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.
apartheid-era security facility
An apartheid-era security facility is a state-controlled compound used by South Africa’s apartheid regime to detain, interrogate, and surveil individuals deemed political threats, often employing coercive and clandestine methods to enforce racial segregation and suppress dissent.
-
C.
colonial-era event
A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
-
D.
South African observance
A South African observance is a culturally or historically significant day, event, or practice recognized within South Africa, often marked by public ceremonies, traditions, or commemorations.
-
E.
anti-apartheid facility
An anti-apartheid facility is a physical or organizational space dedicated to resisting, undermining, and ultimately dismantling apartheid systems through activism, support services, coordination, and education.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:55 a.m.