Triple
T10240124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chief Marshal of the branch |
E243565
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Soviet military rank |
C15456
|
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 Context triple: [Chief Marshal of the branch, instanceOf, Soviet military rank]
-
A.
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.
-
B.
North Korean military rank
A North Korean military rank is a formal title within the Korean People's Army hierarchy that signifies an individual's level of authority, responsibility, and status in the armed forces of the Democratic People's Republic of Korea.
-
C.
historical military rank
chosen
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.
-
D.
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.
-
E.
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.
- 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.