Triple
T7512217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Inspector-General of Armoured Troops |
E177547
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Wehrmacht position |
C22492
|
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: Wehrmacht position Context triple: [Inspector-General of Armoured Troops, instanceOf, Wehrmacht position]
-
A.
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.
-
B.
Imperial Japanese Army position
An Imperial Japanese Army position is a specific military role or rank within the land forces of the Empire of Japan, defining an individual's authority, responsibilities, and place in the army hierarchy.
-
C.
Luftwaffe command position
A Luftwaffe command position is an organizational role within the German air force hierarchy responsible for directing air operations, managing resources, and implementing strategic and tactical decisions.
-
D.
Wehrmacht headquarters
The Wehrmacht headquarters was the central command authority of Nazi Germany's unified armed forces, responsible for strategic planning, coordination, and direction of military operations during World War II.
-
E.
army of the Wehrmacht
The army of the Wehrmacht was Nazi Germany’s unified land warfare force from 1935 to 1945, responsible for conducting large-scale military operations and invasions across Europe and beyond during World War II.
- 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_69c69f276b108190af2cc790b6554544 |
completed | March 27, 2026, 3:15 p.m. |
Created at: March 27, 2026, 3:45 p.m.