Triple
T1263972
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Friedrich Wilhelm von Steuben |
E12560
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian military officer |
C449
|
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: Prussian military officer Context triple: [Friedrich Wilhelm von Steuben, instanceOf, Prussian military officer]
-
A.
military officer
chosen
A military officer is a formally commissioned leader in the armed forces responsible for planning, directing, and managing operations, personnel, and resources to achieve strategic and tactical objectives.
-
B.
military reformer
A military reformer is an individual who critically evaluates existing armed forces structures, doctrines, and practices and implements innovative changes to improve their effectiveness, efficiency, and adaptability.
-
C.
King in Prussia
King in Prussia was the royal title used by the Hohenzollern rulers of Brandenburg-Prussia from 1701 to 1772, signifying their kingship over Prussia while remaining nominally subordinate to the Holy Roman Emperor within the empire.
-
D.
German Emperor
A German Emperor is the sovereign ruler who held the imperial title over the German Empire, symbolizing supreme political and military authority within the unified German state from 1871 to 1918.
-
E.
Nazi official
A Nazi official is a person who held an administrative, political, or military position within the National Socialist (Nazi) regime in Germany, responsible for implementing and enforcing its totalitarian, racist, and genocidal policies.
- 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_69a4933352e08190ac617291985e76c0 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:50 p.m.