Triple
T37703425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bladensburg Road near Centreville |
E939129
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Civil War military location |
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 military location Context triple: [Bladensburg Road near Centreville, instanceOf, Civil War military location]
-
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.
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.
-
D.
War of 1812 site
A War of 1812 site is a historically significant location directly associated with military, political, or civilian events of the War of 1812, such as battlefields, forts, encampments, or related structures and landscapes.
-
E.
Revolutionary War site
A Revolutionary War site is a historically significant location where events, battles, encampments, or strategic activities related to the American Revolutionary War took place and are preserved or interpreted today.
- 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_69f76edb49dc8190b951dce9ce6ef789 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:18 p.m.