Triple
T33066435
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian–Russian front of the Seven Years' War |
E846112
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Front |
C33027
|
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 Context triple: [Prussian–Russian front of the Seven Years' War, instanceOf, Eastern Front]
-
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
chosen
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.
Balkan campaign
The Balkan campaign refers to the series of military operations and strategic maneuvers conducted in the Balkan Peninsula during a specific conflict, often involving multiple regional and great powers competing for territorial control and political influence.
-
E.
invasion of Russia
Invasion of Russia is a large-scale military campaign in which foreign forces attempt to penetrate, occupy, or subdue Russian territory, often facing vast distances, harsh climate, and strong defensive resistance.
- 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_69f3495405b88190967af2157b43b896 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:25 a.m.