Triple
T16757161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Military Police Command of the Bundeswehr |
E407238
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | military police command |
C37984
|
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: military police command Context triple: [Military Police Command of the Bundeswehr, instanceOf, military police command]
-
A.
military special operations command
A military special operations command is a specialized organizational unit responsible for planning, directing, and executing high-risk, strategically critical missions using elite, highly trained forces.
-
B.
Indian Army command
Indian Army command is an organizational unit responsible for directing, coordinating, and controlling military operations, administration, and logistics within a defined geographic or functional area of the Indian Army.
-
C.
members of the Royal Military Police
Members of the Royal Military Police are specialized military personnel responsible for policing, law enforcement, and investigative duties within the armed forces, both in the UK and on overseas deployments.
-
D.
army commander post
An army commander post is a designated command facility or position from which a military commander directs, coordinates, and controls the operations of assigned forces.
-
E.
military administration
Military administration is the organizational and managerial framework responsible for planning, directing, and overseeing the personnel, resources, logistics, and policies that enable a military force to function effectively.
- 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_69d8839174188190909f190097207065 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:21 a.m.