Merge NLP module fixes/improvements

[ronentk]

#116 - adding itemtype and quote tweet relations to parser semantics

thread trimming

#105 add thread trimming option
bug fix
#117

[gitguardian]

⚠️ GitGuardian has uncovered 4 secrets following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secrets in your pull request

GitGuardian id	GitGuardian status	Secret	Commit	Filename
11699671	Triggered	Generic High Entropy Secret	976f162	nlp/notebooks/XdatasetLogEdit.ipynb	View secret
12247943	Triggered	Generic High Entropy Secret	e7ec87f	app/firebase/functions/test/tests/user.timeline.result.mock.json	View secret
12247944	Triggered	Generic High Entropy Secret	98f411e	app/firebase/functions/test/tests/user.timeline.result.mock.json	View secret
12247944	Triggered	Generic High Entropy Secret	e7ec87f	app/firebase/functions/test/tests/user.timeline.result.mock.json	View secret

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code.
2. Replace and store your secrets safely. Learn here the best practices.
3. Revoke and rotate these secrets.
4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider

• following these best practices for managing and storing secrets including API keys and other credentials
• install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.

---

^{🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.}