Triple
T4799897
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Field Marshal (Russian Empire) |
E106806
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | rank of the Imperial Russian Army |
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: rank of the Imperial Russian Army Context triple: [Field Marshal (Russian Empire), instanceOf, rank of the Imperial Russian Army]
-
A.
royal army
A royal army is a formally organized, state-sanctioned military force that serves, protects, and enforces the authority and interests of a monarchy.
-
B.
oblast of the Russian Empire
An oblast of the Russian Empire was an administrative-territorial unit, typically on the empire’s periphery, governed by appointed officials and possessing a lower status than a governorate (guberniya).
-
C.
armoured army
An armoured army is a military force primarily composed of heavily protected, mechanized units such as tanks and armored vehicles designed for high-mobility, high-impact ground warfare.
-
D.
army of the Wehrmacht
The army of the Wehrmacht was Nazi Germany’s unified land warfare force from 1935 to 1945, responsible for conducting large-scale military operations and invasions across Europe and beyond during World War II.
-
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_69bd43f6a1e08190bf0a372bfc336ee5 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:23 p.m.