Triple
T1871510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OKH |
E39045
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | German Army command |
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: German Army command Context triple: [OKH, instanceOf, German Army command]
-
A.
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.
-
B.
German soldiers
German soldiers are military personnel serving in Germany’s armed forces, historically or presently, who are trained, organized, and equipped to conduct defense and combat operations under German command.
-
C.
Nazi Germany military rank
A Nazi Germany military rank represents a specific hierarchical position within the armed forces of the Third Reich, defining an individual's authority, responsibilities, and status in the military structure.
-
D.
United States Army command
The United States Army command is the organizational structure and authority framework responsible for directing, coordinating, and controlling Army forces and operations to accomplish national defense objectives.
-
E.
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.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:34 p.m.