Skip to content
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

Use prelabeling (precomputed suggestions) in NER task #118

Closed
gf0507033 opened this issue Nov 8, 2019 · 8 comments
Closed

Use prelabeling (precomputed suggestions) in NER task #118

gf0507033 opened this issue Nov 8, 2019 · 8 comments
Assignees

Comments

@gf0507033
Copy link

Hello, thx for great work!

I'm stuck on simple problem. Can I add to tasks.json field (compatible with completion's result field) with precomputed suggestions? I.e. my goal is to verify or modify existing markup, not to create one.

And one more question: can I add bunch of classification fields to NER task?

@draganrakas
Copy link

+1 for this!

This tool is great, and having the ability to support precomputed suggestions would be a huge improvement for our use case as well!

@gf0507033 gf0507033 changed the title Use precomputed suggestions in NER task Use prelabeling (precomputed suggestions) in NER task Nov 12, 2019
@deppp
Copy link
Collaborator

deppp commented Nov 13, 2019

Hey @gf0507033 and @draganrakas

Just want to let you know that we're currently working on this, and it's gonna be included in one of the next releases. I'll update you on our progress here.

Stay tuned!

@makseq
Copy link
Member

makseq commented Nov 14, 2019

Hi, @gf0507033 and @draganrakas, I've implemented predictions here: #118

Let's check it together. The receipt is:

  1. open tasks.json,
  2. add "predictions": [ {...}, {...} ] to each task inside,
  3. the format of prediction is the same as completion BUT:
    a) exclude "id" field from prediction
    b) add "model_version": "version 1" (optional)
    c) add "created_ago": "1 hour" (optional)

The example could be found here: https://github.com/heartexlabs/label-studio/blob/2f3d85c479171d235d1f1fd1742dcd7736ac3dab/examples/named_entity/tasks.json

So, it will be great if you write me feedback!

@vade
Copy link

vade commented Nov 15, 2019

Some feedback - does it make sense for a static json file to have a relative time offset?

May I suggest having an optional "created" with a date time string rather than "created_ago"? The UI could then handle logic to dynamically say, 3 days ago, then tomorrow, 4 days, or alternatively just show the absolute date which also seems reasonable.

BTW, this project is awesome, and is already proving hugely helpful and very easy to set up. So thank you!

@makseq
Copy link
Member

makseq commented Nov 15, 2019

@vade Thank you for your feedback!
"created" is a good idea. But right now you can use "created_ago" as "created" because it's a simple string. It's a little big crooked but working :-)

@vade
Copy link

vade commented Nov 15, 2019

Oh I see. Ha. Makes sense. Thanks for the quick reply.

@draganrakas
Copy link

Love the change, looking forward to the release. Thank you!

@niklub
Copy link
Collaborator

niklub commented Nov 28, 2019

We've added full support for prelabeling in https://github.com/heartexlabs/label-studio/releases/tag/v0.2.2

@niklub niklub closed this as completed Nov 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants