doc/HIGHLEVEL.md: Theory docs on the extra Evidence Gathering pipeline stage
doc/HIGHLEVEL.md: Update the pipeline flow summary
LATByDBpedia: Produce a debug print only when we have something to report
Fix DKpro version at 1.7.0, just released
LATByFocus: Generate LAT for W- words with specificity 0.0

Previously, we lowered this to avoid ClueLAT. Now, we solve that by
generating instances of a new subclass ImplicitQLAT.
Passage TyCor: Add debug prints tied to type coercion happenning
AnswerGSHook: New property cz.brmlab.yodaqa.csv_answer to generate answer feature breakdowns, one CSV per question
DBpediaRelationPrimarySearch: Do not perform passage tycor

This would always happen the way we compose the title.
answer LATBy*: Do not sum up the LATFeature values, just set to 1.0 once

Our LAT features would represent as many times as we generated any hits,
reaching even 30 or 40 for dbpedia or wninstance sometimes. These
features should be just binary, though.
AnswerScoreLogistic: Retrained with updated model
AnswerScoreLogistic: Retrained with updated model
Merge branch 'f/qsp0'
Merge branch 'f/latfvmax'

Conflicts:
	src/main/java/cz/brmlab/yodaqa/analysis/answer/AnswerScoreLogistic.java
AnswerScoreLogistic: Retrained with updated model
Merge branch 'master' into evidence
Merge branch 'master' into f/dbpnoptycor
AnswerScoreLogistic: Retrained with updated model
doc/HIGHLEVEL: Clarify the 'Answer Analysis' phase description
YodaQA pipeline: Unroll createAnswerMergeAndScoreDescription()

We will want to add some flow control in the middle of that.
YodaQA pipeline: Add support for AnswerHitlist (de)serialization

We can now save the AnswerHitlist before final scoring, and restart
the pipeline only for re-scoring.  This means we do not have to
rerun the whole process when we re-train AnswerScore* but just
re-run the scoring.  (The scripts still need to be tweaked for this.)

(While this is pretty nice in itself, this is going to be quite
essential when evidence gathering and second phase scoring is
implemented.  We will have two serialization points then.)