Triple
T1620497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South African general election, 1989 |
E35019
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in South African history |
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 South African history Context triple: [South African general election, 1989, instanceOf, event in South African history]
-
A.
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.
-
B.
South African person
A South African person is an individual who holds South African nationality or identity, shaped by the country’s diverse cultures, histories, and languages.
-
C.
event in Irish history
An event in Irish history is a significant occurrence or series of actions within Ireland’s past that influenced its political, social, cultural, or economic development.
-
D.
event in the Indian independence movement
An event in the Indian independence movement is a historically significant occurrence—such as a protest, law, campaign, negotiation, or act of resistance—that contributed to India’s struggle to end British colonial rule.
-
E.
Reconstruction-era event
A Reconstruction-era event is a significant historical occurrence between 1865 and 1877 in the United States that shaped the political, social, and economic transformation of the post–Civil War South and the reintegration of formerly seceded states into the Union.
- F. None of above. chosen
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_69a886023194819080a3fccd6e325d0e |
completed | March 4, 2026, 7:20 p.m. |
Created at: March 4, 2026, 7:28 p.m.