Triple
T17442689
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Generalissimo of the Russian land and sea forces |
E424696
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Russian 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: Imperial Russian military rank Context triple: [Generalissimo of the Russian land and sea forces, instanceOf, Imperial Russian 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.
Imperial Japanese military rank
Imperial Japanese military rank is a hierarchical designation used in the armed forces of the Empire of Japan to define authority, responsibility, and status among its military personnel.
-
C.
imperial Russian order
An imperial Russian order is a formal honor or decoration bestowed by the Russian Empire to recognize distinguished service, loyalty, or achievement, typically organized into ranks and worn as insignia.
-
D.
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.
-
E.
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.
- 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_69d889db0ba481908402409af3b37917 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:47 a.m.