Triple
T34330184
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savage’s Station on the Richmond and York River Railroad |
E880981
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil War field hospital site |
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 field hospital site Context triple: [Savage’s Station on the Richmond and York River Railroad, instanceOf, Civil War field hospital site]
-
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 Military Park
A United States National Military Park is a federally protected area that preserves and interprets significant military battlefields or related historic sites for public education, commemoration, and recreation.
-
D.
Historic site
A historic site is a location of significant past events, structures, or cultural heritage that is preserved and recognized for its historical importance.
-
E.
Confederate cemetery
A Confederate cemetery is a burial ground dedicated to interring soldiers and individuals associated with the Confederate States of America, often marked by period-specific monuments and memorials.
- 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_69f349ba96a08190b94887bae2d8ee49 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:58 a.m.