Triple
T26297363
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austro-Russian front in Galicia |
E661452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Front theater of World War I |
C5649
|
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: Eastern Front theater of World War I Context triple: [Austro-Russian front in Galicia, instanceOf, Eastern Front theater of World War I]
-
A.
Eastern Front campaign
The Eastern Front campaign is a large-scale military operation or series of operations conducted on the eastern theater of war, typically involving prolonged, high-intensity ground combat across vast territories between major opposing powers.
-
B.
Eastern Front sector
An Eastern Front sector is a defined geographic portion of the Eastern Front where military forces conduct coordinated operations, defense, and logistics within a larger theater of war.
-
C.
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.
-
D.
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.
-
E.
World War I theater
chosen
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.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
Created at: April 26, 2026, 10:13 p.m.