Triple
T16783126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World War I battlefields |
E407904
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | war-related site |
C15869
|
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: war-related site Context triple: [World War I battlefields, instanceOf, war-related site]
-
A.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
B.
war crime site
A war crime site is a specific location where serious violations of the laws and customs of war have been committed, investigated, or memorialized, often serving as evidence in legal proceedings and as a place of historical record.
-
C.
World War I site
chosen
A World War I site is a historically significant location directly associated with events, operations, or impacts of the First World War, such as battlefields, trenches, memorials, cemeteries, or military installations.
-
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.
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.
- 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_69d8839270588190886720d9519bbf8f |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.