Triple
T7808833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commander of the Voronezh Front |
E180625
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military rank position |
C22945
|
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 rank position Context triple: [Commander of the Voronezh Front, instanceOf, Soviet military rank position]
-
A.
historical military rank
A historical military rank is a formally defined level of authority and responsibility within past armed forces, reflecting the hierarchical structure, duties, and social status of military personnel in a specific historical context.
-
B.
military rank structure
A military rank structure is a hierarchical system that organizes service members into levels of authority and responsibility, defining command relationships, roles, and progression within the armed forces.
-
C.
Nazi Germany military rank
A Nazi Germany military rank represents a specific hierarchical position within the armed forces of the Third Reich, defining an individual's authority, responsibilities, and status in the military structure.
-
D.
military honorific designation
A military honorific designation is a formal title or label conferred upon individuals, units, or formations to recognize distinguished service, valor, heritage, or special status within the armed forces.
-
E.
paramilitary rank
A paramilitary rank is a hierarchical title or position within an organized, non-military armed group that mirrors military ranking structures to define authority, responsibility, and command.
- 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_69ca827f6f148190beca4e245b993506 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:36 p.m.