Triple
T37173468
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Confederate monument controversy |
E920976
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical memory debate |
C25429
|
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: historical memory debate Context triple: [Confederate monument controversy, instanceOf, historical memory debate]
-
A.
historical reflection
Historical reflection is the thoughtful examination and interpretation of past events, contexts, and perspectives to understand their causes, consequences, and relevance to the present.
-
B.
historical recognition
chosen
Historical recognition is the process by which individuals, events, or groups from the past are acknowledged, interpreted, and valued within collective memory and official narratives.
-
C.
cultural heritage dispute
A cultural heritage dispute is a conflict between individuals, groups, or states over the ownership, control, interpretation, or repatriation of culturally significant objects, sites, or traditions.
-
D.
historical topic
A historical topic is a specific subject, event, period, or theme from the past that is studied, analyzed, and interpreted to understand historical developments and their impact.
-
E.
American Civil War memory tradition
American Civil War memory tradition is the evolving set of narratives, commemorations, symbols, and cultural practices through which different groups in the United States have interpreted, justified, contested, and remembered the causes, events, and consequences of the Civil War over time.
- 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_69f76ea16f288190b445aa1604d996f4 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:15 p.m.