Triple
T8912155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somme 1916 |
E212209
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Western Front battle |
C4318
|
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: Western Front battle Context triple: [Somme 1916, instanceOf, Western Front battle]
-
A.
European war
A European war is a large-scale armed conflict primarily involving multiple nation-states within Europe, often driven by territorial, political, or ideological disputes that significantly reshape the continent’s balance of power.
-
B.
World War I battle
chosen
A World War I battle is a large-scale, often prolonged military engagement between opposing forces during the 1914–1918 global conflict, characterized by trench warfare, industrialized weaponry, and significant casualties.
-
C.
World War II front
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
D.
battle of the Franco-Prussian War
A battle of the Franco-Prussian War is a specific military engagement between French and Prussian (and allied German) forces during the 1870–1871 conflict, characterized by defined participants, location, date, tactics, and outcome.
-
E.
World War I site
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.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
Created at: March 30, 2026, 6:56 p.m.