Triple
T24403375
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | first-day field of the Battle of Gettysburg |
E615240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil War battlefield area |
C11829
|
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: Civil War battlefield area Context triple: [first-day field of the Battle of Gettysburg, instanceOf, Civil War battlefield area]
-
A.
Civil War site
chosen
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.
-
B.
American Civil War era site
An American Civil War era site is a historically significant location—such as a battlefield, fort, encampment, prison, or related structure—directly associated with military, political, or social events of the United States Civil War (1861–1865).
-
C.
United States national battlefield
A United States national battlefield is a protected area designated by the federal government to preserve and interpret the site of a significant historic battle, typically from the American Civil War, for public education and commemoration.
-
D.
historic battlefield
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
-
E.
civil war theatre
A civil war theatre is a defined geographic region or operational domain within a civil war where military, political, and social conflicts are concentrated and coordinated.
- 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_69e2d7e780bc81908049c779e697a7f6 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:05 a.m.