Triple
T4023320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allied Supreme War Council |
E91330
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War I organization |
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 organization Context triple: [Allied Supreme War Council, instanceOf, World War I organization]
-
A.
World War I coalition
chosen
A World War I coalition is a group of allied nations that coordinated their military, political, and economic efforts against a common enemy bloc during the First World War.
-
B.
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.
-
C.
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.
-
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-era polity
A World War I-era polity is a sovereign or semi-sovereign political entity that existed and exercised governmental authority during the period surrounding the First World War (circa 1914–1918), shaped by the war’s diplomatic, military, and social upheavals.
- 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_69aed9618b04819081750d979d2af098 |
completed | March 9, 2026, 2:29 p.m. |
Created at: March 9, 2026, 3:35 p.m.