Triple
T37078567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chickahominy Bluff |
E917781
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battlefield landscape |
C2871
|
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 landscape Context triple: [Chickahominy Bluff, instanceOf, battlefield landscape]
-
A.
battlefield feature
A battlefield feature is any physical or environmental characteristic of the combat area—such as terrain, obstacles, or man-made structures—that influences tactics, movement, visibility, and the outcome of military engagements.
-
B.
legendary battlefield
A legendary battlefield is a historically or mythically renowned site where a pivotal, large-scale conflict occurred, leaving lasting cultural, strategic, or symbolic significance.
-
C.
battle course
A battle course is a structured training environment or program designed to simulate combat scenarios and develop participants’ tactical, physical, and strategic skills.
-
D.
historic battlefield
chosen
A historic battlefield is a geographically defined site where significant military engagements occurred, preserved or recognized for its cultural, educational, and commemorative value.
-
E.
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.
- 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_69f76e9771e08190a690834e3cd20654 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.