-
Notifications
You must be signed in to change notification settings - Fork 503
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[DOC] Tokenizers - Classic #8357
base: main
Are you sure you want to change the base?
[DOC] Tokenizers - Classic #8357
Conversation
Signed-off-by: [email protected] <[email protected]>
Signed-off-by: [email protected] <[email protected]>
Thank you for submitting your PR. The PR states are In progress (or Draft) -> Tech review -> Doc review -> Editorial review -> Merged. Before you submit your PR for doc review, make sure the content is technically accurate. If you need help finding a tech reviewer, tag a maintainer. When you're ready for doc review, tag the assignee of this PR. The doc reviewer may push edits to the PR directly or leave comments and editorial suggestions for you to address (let us know in a comment if you have a preference). The doc reviewer will arrange for an editorial review. |
@udabhas Will you review this PR for technical accuracy, or have a peer review it? Thank you. |
Signed-off-by: [email protected] <[email protected]>
Signed-off-by: [email protected] <[email protected]>
By analyzing the text "Send an email to [email protected] or call 555-1234!", we can see the punctuation has been removed, while email and phone number | ||
|
||
``` | ||
"Send", "an", "email", "to", "john.doe", "example.com", "or", "call", "555-1234" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: I was wondering if it would be better to show entire output as there are different token types.
{"<ALPHANUM>", "<APOSTROPHE>", "<ACRONYM>", "<COMPANY>", "<EMAIL>", "<HOST>", "<NUM>", "<CJ>", "<ACRONYM_DEP>"}
{
"tokens": [
{
"token": "Send",
"start_offset": 0,
"end_offset": 4,
"type": "<ALPHANUM>",
"position": 0
},
{
"token": "an",
"start_offset": 5,
"end_offset": 7,
"type": "<ALPHANUM>",
"position": 1
},
{
"token": "email",
"start_offset": 8,
"end_offset": 13,
"type": "<ALPHANUM>",
"position": 2
},
{
"token": "to",
"start_offset": 14,
"end_offset": 16,
"type": "<ALPHANUM>",
"position": 3
},
{
"token": "[email protected]",
"start_offset": 17,
"end_offset": 37,
"type": "<EMAIL>",
"position": 4
},
{
"token": "or",
"start_offset": 38,
"end_offset": 40,
"type": "<ALPHANUM>",
"position": 5
},
{
"token": "call",
"start_offset": 41,
"end_offset": 45,
"type": "<ALPHANUM>",
"position": 6
},
{
"token": "555-1234",
"start_offset": 46,
"end_offset": 54,
"type": "<NUM>",
"position": 7
}
]
}
Description
Addition of the Tokenizer - Classic documentation, to the Analyzers section.
Issues Resolved
Part of #1483 addressed in this PR.
Version
All
Frontend features
n/a
Checklist
For more information on following Developer Certificate of Origin and signing off your commits, please check here.