Triple
T721986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mesopotamian campaign (World War I) |
E14636
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theatre of World War I |
C4513
|
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: theatre of World War I Context triple: [Mesopotamian campaign (World War I), instanceOf, theatre of World War I]
-
A.
theater of World War II
The theater of World War II is a conceptual class representing a distinct geographic region and operational context in which military campaigns, battles, and strategic activities of the war were planned, conducted, and coordinated.
-
B.
World War I film
A World War I film is a motion picture that dramatizes events, experiences, and themes related to the First World War, often focusing on the human, political, and military dimensions of the conflict.
-
C.
World War I poster
A World War I poster is a visually striking, often propagandistic print designed to influence public opinion or behavior during the war, typically through patriotic imagery, bold text, and emotional appeals.
-
D.
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.
-
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_69a4934c753c81909b309027e48b9b3a |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:37 p.m.