Triple
T30367744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Belgorod sector |
E772465
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | World War II military operational area |
C4875
|
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 II military operational area Context triple: [Belgorod sector, instanceOf, World War II military operational area]
-
A.
World War II rear area
A World War II rear area is the zone behind the front lines where military forces organized logistics, supply, administration, medical care, training, and security operations to support combat units at the front.
-
B.
World War II site
A World War II site is a historically significant location directly associated with events, operations, or impacts of the Second World War, preserved or recognized for its cultural, military, or memorial value.
-
C.
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.
-
D.
World War II front
chosen
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.
-
E.
World War II Allied operation
A World War II Allied operation is a coordinated military campaign or mission planned and executed by the Allied powers to achieve specific strategic, tactical, or logistical objectives against the Axis forces.
- 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_69f2248d71408190aec0d5c2001b1cff |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 7:59 p.m.