Triple
T38532674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial Russian military ranks |
E923409
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical military hierarchy |
C1739
|
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: historical military hierarchy Context triple: [Imperial Russian military ranks, instanceOf, historical military hierarchy]
-
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.
historical armed forces
Historical armed forces are organized military institutions from past eras, composed of soldiers, equipment, and command structures, created by states or societies to conduct warfare, defend territories, and project power.
-
C.
military rank structure
chosen
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.
military history reference
A military history reference is a comprehensive resource that systematically documents, analyzes, and contextualizes past armed conflicts, strategies, technologies, and key figures for study and research.
-
E.
military history
Military history is the study of armed conflict across time, examining wars, battles, strategies, technologies, and their political, social, and cultural impacts on societies.
- 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_69f76ea8f6348190a5c03fb6292bbee3 |
completed | May 3, 2026, 3:50 p.m. |
Created at: May 3, 2026, 4:32 p.m.