Added new kpwr model

README

@@ -33,7 +33,7 @@ type as a separate channel, Iobber may treat several chunk types as one
 "layer", effectively treating them as one channel. This means that no chunks
 from a given layer may overlap.
 
-The kpwr.ini config (and its trained model -- model-kpwr03) defines two layers:
+The kpwr.ini config (and its trained model -- model-kpwr04) defines two layers:
 * layer1 with simple agreement-based noun/adj phrases: chunk_agp,
 * layer2 with phrases based on pred-arg structure: chunk_np, chunk_adjp and
 chunk_vp.
@@ -52,7 +52,7 @@ files already annotated with named entities).
 
 Example call using the bundled model:
 
-iobber kpwr.ini -d model-kpwr03/ my_xces_input.xml -i xces -O ccl_chunked_output.xml
+iobber kpwr.ini -d model-kpwr04/ my_xces_input.xml -i xces -O ccl_chunked_output.xml
 
 This will read the given XCES-encoded file and produce CCL output. Note: the
 kpwr.ini config assumes the input file has been morphosyntactically tagged and