Triple
T870527
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Powers |
E18801
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I coalition |
C5547
|
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 coalition Context triple: [Central Powers, instanceOf, World War I coalition]
-
A.
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.
-
B.
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.
-
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.
League of Nations body
A League of Nations body is an organizational unit or agency established under the League of Nations to carry out specific functions such as maintaining peace, overseeing mandates, resolving disputes, or coordinating international cooperation among member states.
-
E.
organ of the League of Nations
An organ of the League of Nations is an institutional body established by the League to perform specific functions such as decision-making, administration, or dispute resolution within the organization’s international governance framework.
- 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_69a4938db1f081909bcd1ad2713b6096 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:39 p.m.