Triple
T4206067
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Bryansk Front |
E93783
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military post |
C4512
|
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: Soviet military post Context triple: [Commander of the Bryansk Front, instanceOf, Soviet military post]
-
A.
military installation
A military installation is a designated facility or area where armed forces are stationed, trained, equipped, and supported to conduct defense and security operations.
-
B.
Soviet military equipment
Soviet military equipment encompasses the weapons, vehicles, and support systems designed and produced by the Soviet Union to equip its armed forces, characterized by rugged construction, mass production, and doctrinal emphasis on large-scale, combined-arms warfare.
-
C.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
-
D.
army commander post
chosen
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
-
E.
Soviet administrative structure
The Soviet administrative structure was a highly centralized, hierarchical system of governance in which the Communist Party controlled state institutions, economic planning, and regional authorities through overlapping layers of bureaucratic and political oversight.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:03 p.m.