Triple
T4209521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Great General Staff |
E93866
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian military organization |
C6537
|
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 organization Context triple: [Great General Staff, instanceOf, Prussian military organization]
-
A.
military district of the Holy Roman Empire
A military district of the Holy Roman Empire was an administrative and territorial unit organized primarily for defense and military command, grouping various imperial estates under a regional military structure.
-
B.
branch of the German Army
chosen
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.
ethnic German militia
An ethnic German militia is an armed, organized group composed primarily of ethnic Germans, typically formed to pursue political, security, or nationalist objectives within a specific region or conflict.
-
D.
Polish military position
A Polish military position is an organized role or rank within Poland's armed forces, defined by specific duties, authority, and responsibilities in the national defense structure.
-
E.
Prussian prince
A Prussian prince is a male royal family member of the Kingdom of Prussia, typically holding hereditary titles, political influence, and social prestige within the Prussian and broader German nobility.
- 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_69b3451743608190808f41d17ccf2650 |
completed | March 12, 2026, 10:58 p.m. |
Created at: March 12, 2026, 11:03 p.m.