Triple
T17353220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Großer Generalstab |
E421864
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Prussian military institution |
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: Prussian military institution Context triple: [Großer Generalstab, instanceOf, Prussian military institution]
-
A.
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.
-
B.
component of the Prussian Army
chosen
A component of the Prussian Army is an organizational subdivision—such as a regiment, corps, or specialized unit—responsible for specific military functions within the broader Prussian military structure.
-
C.
Polish military institution
A Polish military institution is an organization established by the Polish state to manage, train, support, or command elements of the armed forces in accordance with national defense policies and legal frameworks.
-
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.
Belgian military institution
A Belgian military institution is an organization within Belgium’s defense structure responsible for training, organizing, and supporting the country’s armed forces in accordance with national and international security objectives.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:44 a.m.