Triple
T15460557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Pozières |
E371886
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engagement of the First World War |
C35474
|
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: engagement of the First World War Context triple: [Battle of Pozières, instanceOf, engagement of the First World War]
-
A.
aspect of World War I
An aspect of World War I is a distinct thematic element—such as military strategy, technological innovation, political diplomacy, social impact, or cultural memory—that characterizes and helps explain the nature and consequences of the conflict.
-
B.
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.
-
C.
engagement of the Hundred Years' War
An engagement of the Hundred Years' War is a specific military confrontation—ranging from major battles to minor skirmishes—fought between English and French (and their allies') forces within the broader conflict spanning 1337 to 1453.
-
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.
participant in World War I
A participant in World War I is any nation, military force, or individual actively involved in the political, military, or logistical operations of the global conflict between 1914 and 1918.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:32 a.m.