Triple
T32931220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shell Crisis of 1915 |
E842404
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I home front event |
C61415
|
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: World War I home front event Context triple: [Shell Crisis of 1915, instanceOf, World War I home front event]
-
A.
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.
-
B.
World War II home front initiative
A World War II home front initiative is a coordinated civilian effort, organized by governments or communities, to support the war through activities such as resource conservation, industrial production, volunteer work, and morale-building campaigns.
-
C.
World War I-era declaration
A World War I-era declaration is a formal, often government-issued statement that announces intentions, positions, or demands related to the political, military, or diplomatic circumstances of the First World War.
-
D.
World War I theater
A World War I theater is a large-scale geographic region where military operations, campaigns, and battles of the First World War were conducted under a unified strategic command.
-
E.
World War I battle
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.
- F. None of above. chosen
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_69f34948adfc8190a937f1f622783c0b |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.