Triple
T9834265
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prussian military medical service |
E239061
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | component of the Prussian Army |
C26926
|
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: component of the Prussian Army Context triple: [Prussian military medical service, instanceOf, component of the Prussian Army]
-
A.
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.
-
B.
branch of the German Army
A branch of the German Army is a specialized organizational subdivision responsible for a distinct set of military functions, capabilities, and operational roles within the overall land forces structure.
-
C.
Prussian general
A Prussian general is a high-ranking military officer of the historical Kingdom of Prussia, characterized by rigorous discipline, strategic planning, and leadership in organizing and commanding armies in war.
-
D.
branch of the Bundeswehr
A branch of the Bundeswehr is a major organizational component of Germany’s armed forces, such as the Army, Navy, or Air Force, each with distinct roles, capabilities, and responsibilities in national defense.
-
E.
Prussian state institution
A Prussian state institution is a formal governmental body or organization established by the Kingdom of Prussia to administer public affairs, implement state policies, and maintain social order within its territories.
- F. None of above. chosen
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_69ca84e314108190978324a4bdb959f8 |
completed | March 30, 2026, 2:12 p.m. |
Created at: March 30, 2026, 8:32 p.m.