Triple
T7911742
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fort Chaplin Park |
E183714
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | American Civil War fort site |
C10504
|
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 fort site Context triple: [Fort Chaplin Park, instanceOf, American Civil War fort site]
-
A.
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.
-
B.
American Civil War era site
chosen
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.
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.
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.
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_69ca828dec0c81908b8f55a4dbbb53ff |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 5:04 p.m.