Triple
T1384351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Sevastopol (1941–1942) |
E29810
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of World War II |
C873
|
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: battle of World War II Context triple: [Siege of Sevastopol (1941–1942), instanceOf, battle of World War II]
-
A.
World War II campaign
A World War II campaign is a coordinated series of military operations conducted over a specific period and geographic area, aimed at achieving strategic objectives within the broader context of the war.
-
B.
phase of World War II
A phase of World War II is a distinct, time-bounded period of the conflict characterized by specific strategic objectives, major campaigns, and shifts in military, political, or economic conditions.
-
C.
World War II front
A World War II front is a large-scale, geographically defined theater of military operations where opposing forces engaged in sustained combat and strategic maneuvers during the Second World War.
-
D.
World War II event
chosen
A World War II event is a historically significant occurrence between 1939 and 1945 that directly influenced the political, military, social, or economic course of the global conflict.
-
E.
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.
- 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_69a498dc92f8819094a1108f8ac90f43 |
completed | March 1, 2026, 7:51 p.m. |
Created at: March 1, 2026, 7:59 p.m.