Triple
T31978044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fugitive's Drift |
E816500
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battlefield-related heritage site |
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-related heritage site Context triple: [Fugitive's Drift, instanceOf, battlefield-related heritage site]
-
A.
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.
-
B.
Cold War military site
A Cold War military site is a strategically located facility, installation, or complex developed or used during the Cold War era for defense, surveillance, weapons deployment, command and control, or related military operations shaped by nuclear deterrence and superpower rivalry.
-
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.
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.
-
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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:11 a.m.