Triple
T34057030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Richmond Association |
E873388
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battlefield preservation organization |
C5566
|
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: battlefield preservation organization Context triple: [Battle of Richmond Association, instanceOf, battlefield preservation organization]
-
A.
battlefield park
A battlefield park is a preserved outdoor area that commemorates and interprets a historic military engagement, often featuring monuments, markers, and landscapes maintained for education and remembrance.
-
B.
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.
-
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 preservation organization
chosen
A historic preservation organization is a group dedicated to identifying, protecting, and promoting buildings, sites, and artifacts of historical, cultural, or architectural significance.
-
E.
military proving ground organization
A military proving ground organization is an entity responsible for planning, conducting, and evaluating tests and experiments of weapons, equipment, and tactics under controlled field conditions to validate performance, safety, and operational effectiveness.
- 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_69f349a3ec2c8190b62da76e54231a0f |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:52 a.m.