Triple
T22280183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Carolina monuments at Gettysburg |
E550710
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Confederate monument group |
C11059
|
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: Confederate monument group Context triple: [North Carolina monuments at Gettysburg, instanceOf, Confederate monument group]
-
A.
Confederate monument
chosen
A Confederate monument is a public structure or statue commemorating individuals, units, or causes associated with the Confederate States of America, often serving as a focal point of historical memory and contemporary controversy.
-
B.
Confederate memorialist
A Confederate memorialist is an individual who advocates for, designs, preserves, or promotes monuments, narratives, and commemorations honoring the Confederate cause or its participants.
-
C.
American Civil War monument
An American Civil War monument is a commemorative structure or sculpture erected to honor individuals, units, or events associated with the United States Civil War, often serving as a site of historical memory and public reflection.
-
D.
supporters' group
A supporters' group is an organized community of fans who collectively back a team, individual, cause, or organization through coordinated activities, events, and expressions of loyalty.
-
E.
Apachean group
An Apachean group is a cultural and linguistic grouping of Native American peoples in the Athabaskan language family, including the Apache and Navajo, who share related languages, histories, and certain cultural traits.
- 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_69e11e44d538819097c6b8f333af3352 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:40 p.m.