Triple
T6798899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Russian Second Army |
E156130
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Russian Army formation |
C19405
|
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 Army formation Context triple: [Russian Second Army, instanceOf, Imperial Russian Army formation]
-
A.
army formation
chosen
An army formation is an organized arrangement of military units and personnel on the battlefield or during maneuvers, designed to optimize command, movement, and combat effectiveness.
-
B.
formation of the Russian Armed Forces
The formation of the Russian Armed Forces is the historical and organizational process through which Russia established, structured, and developed its modern military institutions, branches, and command systems following the dissolution of the Soviet Union.
-
C.
French Army formation
A French Army formation is an organized military unit or grouping within the French Army, structured and equipped to conduct specific operational, tactical, or administrative functions.
-
D.
Prussian Army regiment
A Prussian Army regiment is a military unit of the Kingdom of Prussia, typically composed of several battalions or squadrons, organized under a unified command structure for tactical, administrative, and ceremonial purposes.
-
E.
Imperial Russian Navy formation
An Imperial Russian Navy formation is an organized grouping of naval vessels, aircraft, and supporting units structured under a unified command to conduct maritime operations for the Russian Empire.
- 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_69c6881844448190a65822d9b39d7f88 |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:15 p.m.