Triple
T10240104
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Komandarm 1st rank |
E243564
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Red Army rank |
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: Red Army rank Context triple: [Komandarm 1st rank, instanceOf, Red Army rank]
-
A.
army rank
An army rank is a formal level of authority and responsibility within a military hierarchy that defines a soldier’s position, duties, and chain-of-command relationships.
-
B.
Soviet military rank position
chosen
A Soviet military rank position represents a specific hierarchical status and role within the armed forces of the former Soviet Union, defining an individual's authority, responsibilities, and command relationships.
-
C.
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.
-
D.
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.
-
E.
military rank group
A military rank group is a classification that organizes individual military ranks into hierarchical categories based on authority, responsibility, and role within the armed forces structure.
- 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_69d381b0f97c819085c9b45799a5fb7c |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:24 a.m.