Triple
T13442496
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orel sector |
E320400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Eastern Front sector |
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 sector Context triple: [Orel sector, instanceOf, Eastern Front sector]
-
A.
German military district
A German military district is a regional administrative and organizational unit of the German armed forces responsible for local command, logistics, personnel management, and military infrastructure within its designated area.
-
B.
Cossack territory
Cossack territory is a semi-autonomous frontier region historically inhabited and governed by Cossack communities, characterized by military service, self-rule, and a distinct cultural identity within larger empires.
-
C.
Soviet field army
A Soviet field army was a large, operational-level military formation of the Soviet Armed Forces, typically comprising multiple corps or divisions, support units, and command structures, organized to conduct sustained offensive or defensive campaigns in a designated theater of operations.
-
D.
Eurasian steppe
The Eurasian steppe is a vast belt of temperate grassland stretching from Eastern Europe across Central Asia to Manchuria, characterized by open plains, continental climate, and a long history of nomadic pastoralism and cultural exchange.
-
E.
Wehrmacht position
A Wehrmacht position is a designated location or role within the German armed forces of Nazi Germany during World War II, encompassing specific duties, rank, and tactical responsibilities in military operations.
- F. None of above. chosen
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_69d80761e6cc8190a90c844589998ecc |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:40 p.m.