Triple
T16522016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Royal Experiment |
E401342
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War program |
C37576
|
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: American Civil War program Context triple: [Port Royal Experiment, instanceOf, American Civil War program]
-
A.
theater of the American Civil War
The theater of the American Civil War is the conceptual domain encompassing the geographic regions, military campaigns, political arenas, and social contexts in which the conflict’s strategies, battles, and narratives unfolded.
-
B.
overland campaign
An overland campaign is a sustained military or strategic operation conducted across land, involving the coordinated movement and engagement of forces over extended distances and time.
-
C.
book about the American Civil War
A book about the American Civil War is a written work that examines the causes, events, key figures, and consequences of the conflict between the Union and Confederacy in the United States from 1861 to 1865.
-
D.
American Civil War document
An American Civil War document is any written, printed, or official record created during or about the U.S. Civil War (1861–1865) that provides evidence of military, political, social, or personal aspects of the conflict.
-
E.
Civil War site
A Civil War site is a historically significant location where events related to the American Civil War occurred, such as battles, encampments, or military operations, and is preserved or recognized for its cultural and educational value.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.