Triple
T26033549
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Denmark Vesey's conspiracy |
E647494
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | event in African-American history |
C50164
|
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 African-American history Context triple: [Denmark Vesey's conspiracy, instanceOf, event in African-American history]
-
A.
African American holiday
An African American holiday is a culturally significant observance that celebrates the history, heritage, struggles, and achievements of African Americans through traditions, rituals, and community activities.
-
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.
African-American cultural landmark
An African-American cultural landmark is a place, structure, or site of historical, artistic, or social significance that embodies and preserves the experiences, achievements, and heritage of African Americans.
-
D.
event in South African history
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.
-
E.
event in Native American history
A significant occurrence or series of actions involving Native American peoples that influenced their societies, cultures, territories, or relationships with other groups at a particular time in history.
- 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_69e77e8b60e88190a3b26c4f0032a2c2 |
completed | April 21, 2026, 1:41 p.m. |
Created at: April 22, 2026, 9:06 a.m.