Triple
T33621829
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marshal of the Russian Federation |
E861292
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | highest military rank of Russia |
C15455
|
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: highest military rank of Russia Context triple: [Marshal of the Russian Federation, instanceOf, highest military rank of Russia]
-
A.
supreme military rank
chosen
A supreme military rank is the highest possible position in a nation's armed forces hierarchy, typically held by a single individual with ultimate authority over all military operations and strategy.
-
B.
Soviet military rank position
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.
Russian field marshal
A Russian field marshal is the highest-ranking military officer in the Russian (historically Imperial or Soviet-equivalent) army, responsible for commanding large-scale operations and shaping overall military strategy.
-
D.
military-equivalent rank
A military-equivalent rank is a formal position or title in a non-military organization that is defined to correspond in status, authority, or protocol to a specific rank within a military hierarchy.
-
E.
military rank and position
A military rank and position represents an individual's formal level of authority and designated role within an armed forces hierarchy, defining their responsibilities, command scope, and relationship to other personnel.
- 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_69f34980fabc81909819228729a9ca84 |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:41 a.m.