English Evaluation Dataset
Collection
42 items
•
Updated
•
7
id
stringlengths 9
12
| query
stringlengths 665
1.43k
| answer
stringlengths 3
1.21k
| label
sequencelengths 1
138
| token
sequencelengths 1
138
|
|---|---|---|---|---|
finerord0 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: H
ave
you
ever
felt
that
sudden
,
intense
dread
that
you
’re
about
to
die
?
Answer: | H:O
ave:O
you:O
ever:O
felt:O
that:O
sudden:O
,:O
intense:O
dread:O
that:O
you:O
’re:O
about:O
to:O
die:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"H",
"ave",
"you",
"ever",
"felt",
"that",
"sudden",
",",
"intense",
"dread",
"that",
"you",
"’re",
"about",
"to",
"die",
"?"
] |
finerord1 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: That
in
less
than
seven
minutes
,
the
knot
of
fear
and
anxiety
unspooling
at
speed
will
swallow
you
whole
,
rendering
your
life
blank
and
your
existence
meaningless
?
Answer: | That:O
in:O
less:O
than:O
seven:O
minutes:O
,:O
the:O
knot:O
of:O
fear:O
and:O
anxiety:O
unspooling:O
at:O
speed:O
will:O
swallow:O
you:O
whole:O
,:O
rendering:O
your:O
life:O
blank:O
and:O
your:O
existence:O
meaningless:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"That",
"in",
"less",
"than",
"seven",
"minutes",
",",
"the",
"knot",
"of",
"fear",
"and",
"anxiety",
"unspooling",
"at",
"speed",
"will",
"swallow",
"you",
"whole",
",",
"rendering",
"your",
"life",
"blank",
"and",
"your",
"existence",
"meaningless",
"?"
] |
finerord2 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: And
all
because
you
failed
to
prepare
!
Answer: | And:O
all:O
because:O
you:O
failed:O
to:O
prepare:O
!:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"And",
"all",
"because",
"you",
"failed",
"to",
"prepare",
"!"
] |
finerord3 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: You
idiot
!
Answer: | You:O
idiot:O
!:O | [
"O",
"O",
"O"
] | [
"You",
"idiot",
"!"
] |
finerord4 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: And
now
you
’re
on
a
train
carriage
in
a
clammy
panic
desperately
searching
for
hope
.
Answer: | And:O
now:O
you:O
’re:O
on:O
a:O
train:O
carriage:O
in:O
a:O
clammy:O
panic:O
desperately:O
searching:O
for:O
hope:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"And",
"now",
"you",
"’re",
"on",
"a",
"train",
"carriage",
"in",
"a",
"clammy",
"panic",
"desperately",
"searching",
"for",
"hope",
"."
] |
finerord5 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Also
known
as
“
a
plug
point
”
.
Answer: | Also:O
known:O
as:O
“:O
a:O
plug:O
point:O
”:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Also",
"known",
"as",
"“",
"a",
"plug",
"point",
"”",
"."
] |
finerord6 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Also
known
as
the
one
thing
keeping
you
connected
and
alive
,
contactable
at
all
times
for
an
urgent
call
about
the
missold
PPI
you
’ve
never
bought
.
Answer: | Also:O
known:O
as:O
the:O
one:O
thing:O
keeping:O
you:O
connected:O
and:O
alive:O
,:O
contactable:O
at:O
all:O
times:O
for:O
an:O
urgent:O
call:O
about:O
the:O
missold:O
PPI:O
you:O
’ve:O
never:O
bought:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Also",
"known",
"as",
"the",
"one",
"thing",
"keeping",
"you",
"connected",
"and",
"alive",
",",
"contactable",
"at",
"all",
"times",
"for",
"an",
"urgent",
"call",
"about",
"the",
"missold",
"PPI",
"you",
"’ve",
"never",
"bought",
"."
] |
finerord7 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Dead
-
battery
anxiety
is
a
thing
.
Answer: | Dead:O
-:O
battery:O
anxiety:O
is:O
a:O
thing:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Dead",
"-",
"battery",
"anxiety",
"is",
"a",
"thing",
"."
] |
finerord8 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Last
week
a
man
named
Robin
Lee
was
told
he
would
be
arrested
,
presumably
for
crimes
against
electricity
,
if
he
refused
to
unplug
his
i
Phone
from
a
socket
on
the
London
Overground
.
Answer: | Last:O
week:O
a:O
man:O
named:O
Robin:B-PER
Lee:I-PER
was:O
told:O
he:O
would:O
be:O
arrested:O
,:O
presumably:O
for:O
crimes:O
against:O
electricity:O
,:O
if:O
he:O
refused:O
to:O
unplug:O
his:O
i:O
Phone:O
from:O
a:O
socket:O
on:O
the:O
London:B-LOC
Overground:I-LOC
.:O | [
"O",
"O",
"O",
"O",
"O",
"B-PER",
"I-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O"
] | [
"Last",
"week",
"a",
"man",
"named",
"Robin",
"Lee",
"was",
"told",
"he",
"would",
"be",
"arrested",
",",
"presumably",
"for",
"crimes",
"against",
"electricity",
",",
"if",
"he",
"refused",
"to",
"unplug",
"his",
"i",
"Phone",
"from",
"a",
"socket",
"on",
"the",
"London",
"Overground",
"."
] |
finerord9 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: He
did
n’t
,
and
he
was
–
only
to
be
“
de-
arrested
”
later
while
self
-
righteously
claiming
“
the
whole
thing
was
ridiculous
”
,
unlike
his
normalised
need
to
be
“
on
”
at
all
times
.
Answer: | He:O
did:O
n’t:O
,:O
and:O
he:O
was:O
–:O
only:O
to:O
be:O
“:O
de-:O
arrested:O
”:O
later:O
while:O
self:O
-:O
righteously:O
claiming:O
“:O
the:O
whole:O
thing:O
was:O
ridiculous:O
”:O
,:O
unlike:O
his:O
normalised:O
need:O
to:O
be:O
“:O
on:O
”:O
at:O
all:O
times:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"He",
"did",
"n’t",
",",
"and",
"he",
"was",
"–",
"only",
"to",
"be",
"“",
"de-",
"arrested",
"”",
"later",
"while",
"self",
"-",
"righteously",
"claiming",
"“",
"the",
"whole",
"thing",
"was",
"ridiculous",
"”",
",",
"unlike",
"his",
"normalised",
"need",
"to",
"be",
"“",
"on",
"”",
"at",
"all",
"times",
"."
] |
finerord10 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: A
woman
on
the
Hong
Kong
public
-
transport
system
dealt
with
her
dead
phone
by
crying
and
screaming
for
help
Answer: | A:O
woman:O
on:O
the:O
Hong:B-LOC
Kong:I-LOC
public:O
-:O
transport:O
system:O
dealt:O
with:O
her:O
dead:O
phone:O
by:O
crying:O
and:O
screaming:O
for:O
help:O | [
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"A",
"woman",
"on",
"the",
"Hong",
"Kong",
"public",
"-",
"transport",
"system",
"dealt",
"with",
"her",
"dead",
"phone",
"by",
"crying",
"and",
"screaming",
"for",
"help"
] |
finerord11 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
week
before
,
19
-
year
-
old
Nick
Silvestri
jumped
on
a
Broadway
stage
and
tried
to
jam
his
phone
in
a
prop
outlet
because
it
was
on
5
%
and
“
Girls
were
calling
all
day
.
Answer: | The:O
week:O
before:O
,:O
19:O
-:O
year:O
-:O
old:O
Nick:B-PER
Silvestri:I-PER
jumped:O
on:O
a:O
Broadway:O
stage:O
and:O
tried:O
to:O
jam:O
his:O
phone:O
in:O
a:O
prop:O
outlet:O
because:O
it:O
was:O
on:O
5:O
%:O
and:O
“:O
Girls:O
were:O
calling:O
all:O
day:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-PER",
"I-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"week",
"before",
",",
"19",
"-",
"year",
"-",
"old",
"Nick",
"Silvestri",
"jumped",
"on",
"a",
"Broadway",
"stage",
"and",
"tried",
"to",
"jam",
"his",
"phone",
"in",
"a",
"prop",
"outlet",
"because",
"it",
"was",
"on",
"5",
"%",
"and",
"“",
"Girls",
"were",
"calling",
"all",
"day",
"."
] |
finerord12 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: What
would
you
do
?
”
.
Answer: | What:O
would:O
you:O
do:O
?:O
”:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"What",
"would",
"you",
"do",
"?",
"”",
"."
] |
finerord13 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: What
would
you
do
?
Answer: | What:O
would:O
you:O
do:O
?:O | [
"O",
"O",
"O",
"O",
"O"
] | [
"What",
"would",
"you",
"do",
"?"
] |
finerord14 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: A
2012
study
shows
that
77
%
of
his
peers
in
the
US
are
nomophobes
–
a
real
-
life
condition
recognised
as
a
fear
of
having
no
mobile
battery
or
coverage
;
one
suffered
by
a
reported
66
%
of
the
British
population
.
Answer: | A:O
2012:O
study:O
shows:O
that:O
77:O
%:O
of:O
his:O
peers:O
in:O
the:O
US:B-LOC
are:O
nomophobes:O
–:O
a:O
real:O
-:O
life:O
condition:O
recognised:O
as:O
a:O
fear:O
of:O
having:O
no:O
mobile:O
battery:O
or:O
coverage:O
;:O
one:O
suffered:O
by:O
a:O
reported:O
66:O
%:O
of:O
the:O
British:O
population:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"A",
"2012",
"study",
"shows",
"that",
"77",
"%",
"of",
"his",
"peers",
"in",
"the",
"US",
"are",
"nomophobes",
"–",
"a",
"real",
"-",
"life",
"condition",
"recognised",
"as",
"a",
"fear",
"of",
"having",
"no",
"mobile",
"battery",
"or",
"coverage",
";",
"one",
"suffered",
"by",
"a",
"reported",
"66",
"%",
"of",
"the",
"British",
"population",
"."
] |
finerord15 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
best
(
or
worst
,
depending
on
how
dependent
you
are
on
your
mobile
)
remains
an
as
-
yet
unnamed
woman
filmed
on
public
transport
in
Hong
Kong
,
dealing
with
her
dead
phone
by
screaming
and
crying
for
help
.
Answer: | The:O
best:O
(:O
or:O
worst:O
,:O
depending:O
on:O
how:O
dependent:O
you:O
are:O
on:O
your:O
mobile:O
):O
remains:O
an:O
as:O
-:O
yet:O
unnamed:O
woman:O
filmed:O
on:O
public:O
transport:O
in:O
Hong:B-LOC
Kong:I-LOC
,:O
dealing:O
with:O
her:O
dead:O
phone:O
by:O
screaming:O
and:O
crying:O
for:O
help:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"best",
"(",
"or",
"worst",
",",
"depending",
"on",
"how",
"dependent",
"you",
"are",
"on",
"your",
"mobile",
")",
"remains",
"an",
"as",
"-",
"yet",
"unnamed",
"woman",
"filmed",
"on",
"public",
"transport",
"in",
"Hong",
"Kong",
",",
"dealing",
"with",
"her",
"dead",
"phone",
"by",
"screaming",
"and",
"crying",
"for",
"help",
"."
] |
finerord16 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: She
’s
hysterically
inconsolable
.
Answer: | She:O
’s:O
hysterically:O
inconsolable:O
.:O | [
"O",
"O",
"O",
"O",
"O"
] | [
"She",
"’s",
"hysterically",
"inconsolable",
"."
] |
finerord17 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Her
phone
remains
dead
,
her
dignity
buried
.
Answer: | Her:O
phone:O
remains:O
dead:O
,:O
her:O
dignity:O
buried:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Her",
"phone",
"remains",
"dead",
",",
"her",
"dignity",
"buried",
"."
] |
finerord18 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: I
do
n’t
want
to
say
we
’ve
all
been
there
,
but
to
a
greater
or
lesser
degree
,
we
have
.
Answer: | I:O
do:O
n’t:O
want:O
to:O
say:O
we:O
’ve:O
all:O
been:O
there:O
,:O
but:O
to:O
a:O
greater:O
or:O
lesser:O
degree:O
,:O
we:O
have:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"I",
"do",
"n’t",
"want",
"to",
"say",
"we",
"’ve",
"all",
"been",
"there",
",",
"but",
"to",
"a",
"greater",
"or",
"lesser",
"degree",
",",
"we",
"have",
"."
] |
finerord19 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: I
get
it
.
Answer: | I:O
get:O
it:O
.:O | [
"O",
"O",
"O",
"O"
] | [
"I",
"get",
"it",
"."
] |
finerord20 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Your
phone
battery
hovers
in
the
red
zone
and
your
brain
hits
auto
-
twitch
,
scanning
the
immediate
vicinity
for
power
.
Answer: | Your:O
phone:O
battery:O
hovers:O
in:O
the:O
red:O
zone:O
and:O
your:O
brain:O
hits:O
auto:O
-:O
twitch:O
,:O
scanning:O
the:O
immediate:O
vicinity:O
for:O
power:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Your",
"phone",
"battery",
"hovers",
"in",
"the",
"red",
"zone",
"and",
"your",
"brain",
"hits",
"auto",
"-",
"twitch",
",",
"scanning",
"the",
"immediate",
"vicinity",
"for",
"power",
"."
] |
finerord21 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: It
’s
a
universal
problem
.
Answer: | It:O
’s:O
a:O
universal:O
problem:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"’s",
"a",
"universal",
"problem",
"."
] |
finerord22 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: It
’s
also
really
easily
fixable
through
self
-
imposed
exposure
therapy
.
Answer: | It:O
’s:O
also:O
really:O
easily:O
fixable:O
through:O
self:O
-:O
imposed:O
exposure:O
therapy:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"’s",
"also",
"really",
"easily",
"fixable",
"through",
"self",
"-",
"imposed",
"exposure",
"therapy",
"."
] |
finerord23 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Take
it
from
an
expert
:
I
’ve
reached
Buddha
levels
of
zen
.
Answer: | Take:O
it:O
from:O
an:O
expert:O
::O
I:O
’ve:O
reached:O
Buddha:B-PER
levels:O
of:O
zen:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-PER",
"O",
"O",
"O",
"O"
] | [
"Take",
"it",
"from",
"an",
"expert",
":",
"I",
"’ve",
"reached",
"Buddha",
"levels",
"of",
"zen",
"."
] |
finerord24 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Not
because
of
any
luddite
tendencies
,
but
because
the
longest
relationship
I
’ve
had
with
a
pristine
i
Phone
is
4
months
;
I
’ve
been
using
and
losing
them
since
2007
.
Answer: | Not:O
because:O
of:O
any:O
luddite:O
tendencies:O
,:O
but:O
because:O
the:O
longest:O
relationship:O
I:O
’ve:O
had:O
with:O
a:O
pristine:O
i:O
Phone:O
is:O
4:O
months:O
;:O
I:O
’ve:O
been:O
using:O
and:O
losing:O
them:O
since:O
2007:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Not",
"because",
"of",
"any",
"luddite",
"tendencies",
",",
"but",
"because",
"the",
"longest",
"relationship",
"I",
"’ve",
"had",
"with",
"a",
"pristine",
"i",
"Phone",
"is",
"4",
"months",
";",
"I",
"’ve",
"been",
"using",
"and",
"losing",
"them",
"since",
"2007",
"."
] |
finerord25 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Keeping
a
tally
of
phones
loved
and
lost
stalled
around
i
Phone
number
13
,
two
summers
ago
.
Answer: | Keeping:O
a:O
tally:O
of:O
phones:O
loved:O
and:O
lost:O
stalled:O
around:O
i:O
Phone:O
number:O
13:O
,:O
two:O
summers:O
ago:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Keeping",
"a",
"tally",
"of",
"phones",
"loved",
"and",
"lost",
"stalled",
"around",
"i",
"Phone",
"number",
"13",
",",
"two",
"summers",
"ago",
"."
] |
finerord26 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: It
gets
easier
to
let
go
of
phone
-
battery
anxiety
when
you
’re
not
that
anxious
about
having
a
phone
in
the
first
place
.
Answer: | It:O
gets:O
easier:O
to:O
let:O
go:O
of:O
phone:O
-:O
battery:O
anxiety:O
when:O
you:O
’re:O
not:O
that:O
anxious:O
about:O
having:O
a:O
phone:O
in:O
the:O
first:O
place:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"gets",
"easier",
"to",
"let",
"go",
"of",
"phone",
"-",
"battery",
"anxiety",
"when",
"you",
"’re",
"not",
"that",
"anxious",
"about",
"having",
"a",
"phone",
"in",
"the",
"first",
"place",
"."
] |
finerord27 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Here
’s
some
tips
to
help
you
cope
:
Answer: | Here:O
’s:O
some:O
tips:O
to:O
help:O
you:O
cope:O
::O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Here",
"’s",
"some",
"tips",
"to",
"help",
"you",
"cope",
":"
] |
finerord28 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Go
cold
turkey
Answer: | Go:O
cold:O
turkey:O | [
"O",
"O",
"O"
] | [
"Go",
"cold",
"turkey"
] |
finerord29 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
first
rule
of
phone
freedom
is
to
have
liberated
yourself
from
your
device
at
least
twice
in
your
life
.
Answer: | The:O
first:O
rule:O
of:O
phone:O
freedom:O
is:O
to:O
have:O
liberated:O
yourself:O
from:O
your:O
device:O
at:O
least:O
twice:O
in:O
your:O
life:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"first",
"rule",
"of",
"phone",
"freedom",
"is",
"to",
"have",
"liberated",
"yourself",
"from",
"your",
"device",
"at",
"least",
"twice",
"in",
"your",
"life",
"."
] |
finerord30 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
first
to
experience
it
,
the
second
to
be
experienced
at
it
.
Answer: | The:O
first:O
to:O
experience:O
it:O
,:O
the:O
second:O
to:O
be:O
experienced:O
at:O
it:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"first",
"to",
"experience",
"it",
",",
"the",
"second",
"to",
"be",
"experienced",
"at",
"it",
"."
] |
finerord31 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
number
of
times
you
lose
it
,
break
it
,
have
it
stolen
,
or
drop
it
in
the
toilet
bowl
after
that
depends
on
how
keen
you
are
to
master
not
caring
about
being
connected
to
the
modern
world
.
Answer: | The:O
number:O
of:O
times:O
you:O
lose:O
it:O
,:O
break:O
it:O
,:O
have:O
it:O
stolen:O
,:O
or:O
drop:O
it:O
in:O
the:O
toilet:O
bowl:O
after:O
that:O
depends:O
on:O
how:O
keen:O
you:O
are:O
to:O
master:O
not:O
caring:O
about:O
being:O
connected:O
to:O
the:O
modern:O
world:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"number",
"of",
"times",
"you",
"lose",
"it",
",",
"break",
"it",
",",
"have",
"it",
"stolen",
",",
"or",
"drop",
"it",
"in",
"the",
"toilet",
"bowl",
"after",
"that",
"depends",
"on",
"how",
"keen",
"you",
"are",
"to",
"master",
"not",
"caring",
"about",
"being",
"connected",
"to",
"the",
"modern",
"world",
"."
] |
finerord32 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Experience
the
real
trauma
Answer: | Experience:O
the:O
real:O
trauma:O | [
"O",
"O",
"O",
"O"
] | [
"Experience",
"the",
"real",
"trauma"
] |
finerord33 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
real
faff
is
n’t
in
being
phoneless
,
it
’s
in
the
interminable
admin
involved
in
getting
re-connected
–
registering
the
police
report
;
the
call
to
your
mobile
network
to
block
your
phone
;
the
plea
to
your
insurance
company
to
file
your
claim
;
the
slog
to
the
DHL
depot
to
pick
up
your
new
phone
because
the
courier
could
n’t
be
bothered
to
ring
your
doorbell
.
Answer: | The:O
real:O
faff:O
is:O
n’t:O
in:O
being:O
phoneless:O
,:O
it:O
’s:O
in:O
the:O
interminable:O
admin:O
involved:O
in:O
getting:O
re-connected:O
–:O
registering:O
the:O
police:O
report:O
;:O
the:O
call:O
to:O
your:O
mobile:O
network:O
to:O
block:O
your:O
phone:O
;:O
the:O
plea:O
to:O
your:O
insurance:O
company:O
to:O
file:O
your:O
claim:O
;:O
the:O
slog:O
to:O
the:O
DHL:B-ORG
depot:O
to:O
pick:O
up:O
your:O
new:O
phone:O
because:O
the:O
courier:O
could:O
n’t:O
be:O
bothered:O
to:O
ring:O
your:O
doorbell:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"real",
"faff",
"is",
"n’t",
"in",
"being",
"phoneless",
",",
"it",
"’s",
"in",
"the",
"interminable",
"admin",
"involved",
"in",
"getting",
"re-connected",
"–",
"registering",
"the",
"police",
"report",
";",
"the",
"call",
"to",
"your",
"mobile",
"network",
"to",
"block",
"your",
"phone",
";",
"the",
"plea",
"to",
"your",
"insurance",
"company",
"to",
"file",
"your",
"claim",
";",
"the",
"slog",
"to",
"the",
"DHL",
"depot",
"to",
"pick",
"up",
"your",
"new",
"phone",
"because",
"the",
"courier",
"could",
"n’t",
"be",
"bothered",
"to",
"ring",
"your",
"doorbell",
"."
] |
finerord34 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Agony
,
but
also
an
excellent
lesson
in
perspective
:
no
power
is
a
temporary
drag
,
but
phone
admin
will
destroy
your
soul
.
Answer: | Agony:O
,:O
but:O
also:O
an:O
excellent:O
lesson:O
in:O
perspective:O
::O
no:O
power:O
is:O
a:O
temporary:O
drag:O
,:O
but:O
phone:O
admin:O
will:O
destroy:O
your:O
soul:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Agony",
",",
"but",
"also",
"an",
"excellent",
"lesson",
"in",
"perspective",
":",
"no",
"power",
"is",
"a",
"temporary",
"drag",
",",
"but",
"phone",
"admin",
"will",
"destroy",
"your",
"soul",
"."
] |
finerord35 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Pretend
not
to
care
Answer: | Pretend:O
not:O
to:O
care:O | [
"O",
"O",
"O",
"O"
] | [
"Pretend",
"not",
"to",
"care"
] |
finerord36 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
third
rule
is
to
establish
a
laissez
-
faire
“
attitude
”
towards
your
phone
as
an
essential
part
of
your
being
.
Answer: | The:O
third:O
rule:O
is:O
to:O
establish:O
a:O
laissez:O
-:O
faire:O
“:O
attitude:O
”:O
towards:O
your:O
phone:O
as:O
an:O
essential:O
part:O
of:O
your:O
being:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"third",
"rule",
"is",
"to",
"establish",
"a",
"laissez",
"-",
"faire",
"“",
"attitude",
"”",
"towards",
"your",
"phone",
"as",
"an",
"essential",
"part",
"of",
"your",
"being",
"."
] |
finerord37 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Friends
of
yours
who
have
n’t
met
one
another
before
will
use
your
haplessness
as
an
easy
thing
to
bond
over
.
Answer: | Friends:O
of:O
yours:O
who:O
have:O
n’t:O
met:O
one:O
another:O
before:O
will:O
use:O
your:O
haplessness:O
as:O
an:O
easy:O
thing:O
to:O
bond:O
over:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Friends",
"of",
"yours",
"who",
"have",
"n’t",
"met",
"one",
"another",
"before",
"will",
"use",
"your",
"haplessness",
"as",
"an",
"easy",
"thing",
"to",
"bond",
"over",
"."
] |
finerord38 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Jokes
will
be
made
about
phones
needing
to
be
made
out
of
velcro
or
sold
to
you
like
mittens
on
string
.
Answer: | Jokes:O
will:O
be:O
made:O
about:O
phones:O
needing:O
to:O
be:O
made:O
out:O
of:O
velcro:O
or:O
sold:O
to:O
you:O
like:O
mittens:O
on:O
string:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Jokes",
"will",
"be",
"made",
"about",
"phones",
"needing",
"to",
"be",
"made",
"out",
"of",
"velcro",
"or",
"sold",
"to",
"you",
"like",
"mittens",
"on",
"string",
"."
] |
finerord39 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: You
’ll
hear
the
same
ones
over
and
over
:
weather
it
.
Answer: | You:O
’ll:O
hear:O
the:O
same:O
ones:O
over:O
and:O
over:O
::O
weather:O
it:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"You",
"’ll",
"hear",
"the",
"same",
"ones",
"over",
"and",
"over",
":",
"weather",
"it",
"."
] |
finerord40 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Have
multiple
backup
plans
(
none
of
which
is
“
buy
a
portable
charger
”
)
Answer: | Have:O
multiple:O
backup:O
plans:O
(:O
none:O
of:O
which:O
is:O
“:O
buy:O
a:O
portable:O
charger:O
”:O
):O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Have",
"multiple",
"backup",
"plans",
"(",
"none",
"of",
"which",
"is",
"“",
"buy",
"a",
"portable",
"charger",
"”",
")"
] |
finerord41 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Sure
,
your
battery
is
dead
,
but
this
is
why
you
also
carry
a
tablet
,
for
that
key
moment
when
you
’re
out
and
can
pull
an
i
Pad
from
your
giant
bag
at
10.37
pm
in
a
restaurant
to
check
exactly
why
50
Cent
has
gone
bankrupt
.
Answer: | Sure:O
,:O
your:O
battery:O
is:O
dead:O
,:O
but:O
this:O
is:O
why:O
you:O
also:O
carry:O
a:O
tablet:O
,:O
for:O
that:O
key:O
moment:O
when:O
you:O
’re:O
out:O
and:O
can:O
pull:O
an:O
i:O
Pad:O
from:O
your:O
giant:O
bag:O
at:O
10.37:O
pm:O
in:O
a:O
restaurant:O
to:O
check:O
exactly:O
why:O
50:O
Cent:O
has:O
gone:O
bankrupt:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Sure",
",",
"your",
"battery",
"is",
"dead",
",",
"but",
"this",
"is",
"why",
"you",
"also",
"carry",
"a",
"tablet",
",",
"for",
"that",
"key",
"moment",
"when",
"you",
"’re",
"out",
"and",
"can",
"pull",
"an",
"i",
"Pad",
"from",
"your",
"giant",
"bag",
"at",
"10.37",
"pm",
"in",
"a",
"restaurant",
"to",
"check",
"exactly",
"why",
"50",
"Cent",
"has",
"gone",
"bankrupt",
"."
] |
finerord42 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: What
,
your
tablet
is
cracked
and
/
or
it
needs
charging
?
Answer: | What:O
,:O
your:O
tablet:O
is:O
cracked:O
and:O
/:O
or:O
it:O
needs:O
charging:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"What",
",",
"your",
"tablet",
"is",
"cracked",
"and",
"/",
"or",
"it",
"needs",
"charging",
"?"
] |
finerord43 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: No
problem
,
you
keep
five
essential
numbers
on
you
at
all
times
,
and
are
always
with
someone
who
wo
n’t
mind
you
using
their
phone
.
Answer: | No:O
problem:O
,:O
you:O
keep:O
five:O
essential:O
numbers:O
on:O
you:O
at:O
all:O
times:O
,:O
and:O
are:O
always:O
with:O
someone:O
who:O
wo:O
n’t:O
mind:O
you:O
using:O
their:O
phone:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"No",
"problem",
",",
"you",
"keep",
"five",
"essential",
"numbers",
"on",
"you",
"at",
"all",
"times",
",",
"and",
"are",
"always",
"with",
"someone",
"who",
"wo",
"n’t",
"mind",
"you",
"using",
"their",
"phone",
"."
] |
finerord44 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Wait
:
no
one
trusts
you
to
ever
go
near
their
expensive
mobile
and
you
’ve
run
out
of
friends
?
Answer: | Wait:O
::O
no:O
one:O
trusts:O
you:O
to:O
ever:O
go:O
near:O
their:O
expensive:O
mobile:O
and:O
you:O
’ve:O
run:O
out:O
of:O
friends:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Wait",
":",
"no",
"one",
"trusts",
"you",
"to",
"ever",
"go",
"near",
"their",
"expensive",
"mobile",
"and",
"you",
"’ve",
"run",
"out",
"of",
"friends",
"?"
] |
finerord45 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Do
n’t
worry
about
it
,
it
’s
really
easy
to
keep
talking
to
this
barman
until
he
says
you
can
i
Message
your
flatmate
to
say
you
’re
going
to
be
late
and
you
do
n’t
have
your
keys
,
please
do
n’t
move
house
.
Answer: | Do:O
n’t:O
worry:O
about:O
it:O
,:O
it:O
’s:O
really:O
easy:O
to:O
keep:O
talking:O
to:O
this:O
barman:O
until:O
he:O
says:O
you:O
can:O
i:O
Message:O
your:O
flatmate:O
to:O
say:O
you:O
’re:O
going:O
to:O
be:O
late:O
and:O
you:O
do:O
n’t:O
have:O
your:O
keys:O
,:O
please:O
do:O
n’t:O
move:O
house:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Do",
"n’t",
"worry",
"about",
"it",
",",
"it",
"’s",
"really",
"easy",
"to",
"keep",
"talking",
"to",
"this",
"barman",
"until",
"he",
"says",
"you",
"can",
"i",
"Message",
"your",
"flatmate",
"to",
"say",
"you",
"’re",
"going",
"to",
"be",
"late",
"and",
"you",
"do",
"n’t",
"have",
"your",
"keys",
",",
"please",
"do",
"n’t",
"move",
"house",
"."
] |
finerord46 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Clearly
I
’m
an
idiot
.
Answer: | Clearly:O
I:O
’m:O
an:O
idiot:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Clearly",
"I",
"’m",
"an",
"idiot",
"."
] |
finerord47 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
then
,
I
figure
,
so
are
you
.
Answer: | But:O
then:O
,:O
I:O
figure:O
,:O
so:O
are:O
you:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"then",
",",
"I",
"figure",
",",
"so",
"are",
"you",
"."
] |
finerord48 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Being
forced
to
live
in
the
moment
is
different
to
evangelically
boring
on
about
it
;
but
if
there
’s
one
thing
worse
than
someone
you
ca
n’t
get
hold
of
,
it
’s
the
person
unable
to
“
go
dark
”
without
bleating
“
do
you
know
where
I
can
charge
my
phone
?
”
to
every
other
person
.
Answer: | Being:O
forced:O
to:O
live:O
in:O
the:O
moment:O
is:O
different:O
to:O
evangelically:O
boring:O
on:O
about:O
it:O
;:O
but:O
if:O
there:O
’s:O
one:O
thing:O
worse:O
than:O
someone:O
you:O
ca:O
n’t:O
get:O
hold:O
of:O
,:O
it:O
’s:O
the:O
person:O
unable:O
to:O
“:O
go:O
dark:O
”:O
without:O
bleating:O
“:O
do:O
you:O
know:O
where:O
I:O
can:O
charge:O
my:O
phone:O
?:O
”:O
to:O
every:O
other:O
person:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Being",
"forced",
"to",
"live",
"in",
"the",
"moment",
"is",
"different",
"to",
"evangelically",
"boring",
"on",
"about",
"it",
";",
"but",
"if",
"there",
"’s",
"one",
"thing",
"worse",
"than",
"someone",
"you",
"ca",
"n’t",
"get",
"hold",
"of",
",",
"it",
"’s",
"the",
"person",
"unable",
"to",
"“",
"go",
"dark",
"”",
"without",
"bleating",
"“",
"do",
"you",
"know",
"where",
"I",
"can",
"charge",
"my",
"phone",
"?",
"”",
"to",
"every",
"other",
"person",
"."
] |
finerord49 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
remember
:
no
major
moment
in
history
will
go
undocumented
because
you
were
n’t
recording
it
.
Answer: | But:O
remember:O
::O
no:O
major:O
moment:O
in:O
history:O
will:O
go:O
undocumented:O
because:O
you:O
were:O
n’t:O
recording:O
it:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"remember",
":",
"no",
"major",
"moment",
"in",
"history",
"will",
"go",
"undocumented",
"because",
"you",
"were",
"n’t",
"recording",
"it",
"."
] |
finerord50 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
two
hours
when
your
phone
died
were
probably
not
the
ones
when
Prince
decided
to
cold
-
call
you
.
Answer: | The:O
two:O
hours:O
when:O
your:O
phone:O
died:O
were:O
probably:O
not:O
the:O
ones:O
when:O
Prince:O
decided:O
to:O
cold:O
-:O
call:O
you:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"two",
"hours",
"when",
"your",
"phone",
"died",
"were",
"probably",
"not",
"the",
"ones",
"when",
"Prince",
"decided",
"to",
"cold",
"-",
"call",
"you",
"."
] |
finerord51 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
biggest
lesson
learnt
when
you
recharge
to
find
no
missed
calls
?
Answer: | The:O
biggest:O
lesson:O
learnt:O
when:O
you:O
recharge:O
to:O
find:O
no:O
missed:O
calls:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"biggest",
"lesson",
"learnt",
"when",
"you",
"recharge",
"to",
"find",
"no",
"missed",
"calls",
"?"
] |
finerord52 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: You
’re
not
as
important
as
you
think
you
are
–
and
if
you
are
,
you
’ll
never
be
that
unreachable
in
the
first
place
.
Answer: | You:O
’re:O
not:O
as:O
important:O
as:O
you:O
think:O
you:O
are:O
–:O
and:O
if:O
you:O
are:O
,:O
you:O
’ll:O
never:O
be:O
that:O
unreachable:O
in:O
the:O
first:O
place:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"You",
"’re",
"not",
"as",
"important",
"as",
"you",
"think",
"you",
"are",
"–",
"and",
"if",
"you",
"are",
",",
"you",
"’ll",
"never",
"be",
"that",
"unreachable",
"in",
"the",
"first",
"place",
"."
] |
finerord53 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Imagine
Google
,
Facebook
and
the
country
's
up
-
and
-
coming
startups
nestled
on
the
glittering
foreshore
of
Sydney
Harbour
.
Answer: | Imagine:O
Google:B-ORG
,:O
Facebook:B-ORG
and:O
the:O
country:O
's:O
up:O
-:O
and:O
-:O
coming:O
startups:O
nestled:O
on:O
the:O
glittering:O
foreshore:O
of:O
Sydney:B-LOC
Harbour:I-LOC
.:O | [
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O"
] | [
"Imagine",
"Google",
",",
"Facebook",
"and",
"the",
"country",
"'s",
"up",
"-",
"and",
"-",
"coming",
"startups",
"nestled",
"on",
"the",
"glittering",
"foreshore",
"of",
"Sydney",
"Harbour",
"."
] |
finerord54 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: That
's
the
NSW
government
's
vision
for
Australia
's
first
tech
district
-
a
`
Silicon
Harbour
'
hub
that
's
home
to
the
country
's
booming
startup
and
tech
scene
.
Answer: | That:O
's:O
the:O
NSW:B-ORG
government:I-ORG
's:O
vision:O
for:O
Australia:B-LOC
's:O
first:O
tech:O
district:O
-:O
a:O
`:O
Silicon:B-LOC
Harbour:I-LOC
':O
hub:O
that:O
's:O
home:O
to:O
the:O
country:O
's:O
booming:O
startup:O
and:O
tech:O
scene:O
.:O | [
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"That",
"'s",
"the",
"NSW",
"government",
"'s",
"vision",
"for",
"Australia",
"'s",
"first",
"tech",
"district",
"-",
"a",
"`",
"Silicon",
"Harbour",
"'",
"hub",
"that",
"'s",
"home",
"to",
"the",
"country",
"'s",
"booming",
"startup",
"and",
"tech",
"scene",
"."
] |
finerord55 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: "
(
It
could
be
)
a
place
where
global
giants
of
tech
and
innovation
work
with
startup
entrepreneurs
,
business
incubators
and
accelerators
,
"
Premier
Mike
Baird
said
before
releasing
a
blueprint
for
the
site
.
Answer: | ":O
(:O
It:O
could:O
be:O
):O
a:O
place:O
where:O
global:O
giants:O
of:O
tech:O
and:O
innovation:O
work:O
with:O
startup:O
entrepreneurs:O
,:O
business:O
incubators:O
and:O
accelerators:O
,:O
":O
Premier:O
Mike:B-PER
Baird:I-PER
said:O
before:O
releasing:O
a:O
blueprint:O
for:O
the:O
site:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-PER",
"I-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"\"",
"(",
"It",
"could",
"be",
")",
"a",
"place",
"where",
"global",
"giants",
"of",
"tech",
"and",
"innovation",
"work",
"with",
"startup",
"entrepreneurs",
",",
"business",
"incubators",
"and",
"accelerators",
",",
"\"",
"Premier",
"Mike",
"Baird",
"said",
"before",
"releasing",
"a",
"blueprint",
"for",
"the",
"site",
"."
] |
finerord56 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: However
wires
are
crossed
on
how
exactly
Mr
Baird
would
transform
the
old
industrial
Bays
Precinct
in
Sydney
's
inner
-
west
-
spanning
Glebe
Island
,
White
Bay
and
Rozelle
-
into
a
thriving
tech
capital
.
Answer: | However:O
wires:O
are:O
crossed:O
on:O
how:O
exactly:O
Mr:O
Baird:B-PER
would:O
transform:O
the:O
old:O
industrial:O
Bays:O
Precinct:O
in:O
Sydney:B-LOC
's:O
inner:B-LOC
-:I-LOC
west:I-LOC
-:I-LOC
spanning:I-LOC
Glebe:I-LOC
Island:I-LOC
,:O
White:B-LOC
Bay:I-LOC
and:O
Rozelle:B-LOC
-:O
into:O
a:O
thriving:O
tech:O
capital:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"B-LOC",
"I-LOC",
"I-LOC",
"I-LOC",
"I-LOC",
"I-LOC",
"I-LOC",
"O",
"B-LOC",
"I-LOC",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
"wires",
"are",
"crossed",
"on",
"how",
"exactly",
"Mr",
"Baird",
"would",
"transform",
"the",
"old",
"industrial",
"Bays",
"Precinct",
"in",
"Sydney",
"'s",
"inner",
"-",
"west",
"-",
"spanning",
"Glebe",
"Island",
",",
"White",
"Bay",
"and",
"Rozelle",
"-",
"into",
"a",
"thriving",
"tech",
"capital",
"."
] |
finerord57 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: While
the
local
tech
industry
has
broadly
welcomed
the
government
's
initiative
,
others
including
the
NSW
Labor
opposition
are
concerned
about
the
site
's
lack
of
public
transport
and
existing
tech
businesses
.
Answer: | While:O
the:O
local:O
tech:O
industry:O
has:O
broadly:O
welcomed:O
the:O
government:O
's:O
initiative:O
,:O
others:O
including:O
the:O
NSW:B-ORG
Labor:I-ORG
opposition:O
are:O
concerned:O
about:O
the:O
site:O
's:O
lack:O
of:O
public:O
transport:O
and:O
existing:O
tech:O
businesses:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"While",
"the",
"local",
"tech",
"industry",
"has",
"broadly",
"welcomed",
"the",
"government",
"'s",
"initiative",
",",
"others",
"including",
"the",
"NSW",
"Labor",
"opposition",
"are",
"concerned",
"about",
"the",
"site",
"'s",
"lack",
"of",
"public",
"transport",
"and",
"existing",
"tech",
"businesses",
"."
] |
finerord58 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
founders
of
Australian
software
giant
Atlassian
had
fiercely
lobbied
the
state
government
to
revitalise
the
existing
Australian
Technology
Park
at
nearby
Redfern
.
Answer: | The:O
founders:O
of:O
Australian:O
software:O
giant:O
Atlassian:B-ORG
had:O
fiercely:O
lobbied:O
the:O
state:O
government:O
to:O
revitalise:O
the:O
existing:O
Australian:B-LOC
Technology:I-LOC
Park:I-LOC
at:O
nearby:O
Redfern:B-LOC
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"I-LOC",
"O",
"O",
"B-LOC",
"O"
] | [
"The",
"founders",
"of",
"Australian",
"software",
"giant",
"Atlassian",
"had",
"fiercely",
"lobbied",
"the",
"state",
"government",
"to",
"revitalise",
"the",
"existing",
"Australian",
"Technology",
"Park",
"at",
"nearby",
"Redfern",
"."
] |
finerord59 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
country
's
most
successful
startup
said
it
was
disappointing
the
government
had
favoured
the
White
Bay
site
over
the
Redfern
centre
,
which
was
close
to
universities
and
public
transport
.
Answer: | The:O
country:O
's:O
most:O
successful:O
startup:O
said:O
it:O
was:O
disappointing:O
the:O
government:O
had:O
favoured:O
the:O
White:B-LOC
Bay:I-LOC
site:O
over:O
the:O
Redfern:B-LOC
centre:I-LOC
,:O
which:O
was:O
close:O
to:O
universities:O
and:O
public:O
transport:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"country",
"'s",
"most",
"successful",
"startup",
"said",
"it",
"was",
"disappointing",
"the",
"government",
"had",
"favoured",
"the",
"White",
"Bay",
"site",
"over",
"the",
"Redfern",
"centre",
",",
"which",
"was",
"close",
"to",
"universities",
"and",
"public",
"transport",
"."
] |
finerord60 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: "
While
harbour
foreshore
views
are
undoubtedly
attractive
,
they
also
command
a
premium
price
,
"
Atlassian
said
in
a
statement
.
Answer: | ":O
While:O
harbour:O
foreshore:O
views:O
are:O
undoubtedly:O
attractive:O
,:O
they:O
also:O
command:O
a:O
premium:O
price:O
,:O
":O
Atlassian:B-ORG
said:O
in:O
a:O
statement:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O"
] | [
"\"",
"While",
"harbour",
"foreshore",
"views",
"are",
"undoubtedly",
"attractive",
",",
"they",
"also",
"command",
"a",
"premium",
"price",
",",
"\"",
"Atlassian",
"said",
"in",
"a",
"statement",
"."
] |
finerord61 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: "
And
with
no
nearby
mass
transit
solution
,
it
means
the
proposal
falls
way
beyond
the
reach
of
the
majority
of
our
start
-
up
community
,
incubators
and
universities
who
form
a
critical
part
of
the
technology
ecosystem
.
"
Answer: | ":O
And:O
with:O
no:O
nearby:O
mass:O
transit:O
solution:O
,:O
it:O
means:O
the:O
proposal:O
falls:O
way:O
beyond:O
the:O
reach:O
of:O
the:O
majority:O
of:O
our:O
start:O
-:O
up:O
community:O
,:O
incubators:O
and:O
universities:O
who:O
form:O
a:O
critical:O
part:O
of:O
the:O
technology:O
ecosystem:O
.:O
":O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"\"",
"And",
"with",
"no",
"nearby",
"mass",
"transit",
"solution",
",",
"it",
"means",
"the",
"proposal",
"falls",
"way",
"beyond",
"the",
"reach",
"of",
"the",
"majority",
"of",
"our",
"start",
"-",
"up",
"community",
",",
"incubators",
"and",
"universities",
"who",
"form",
"a",
"critical",
"part",
"of",
"the",
"technology",
"ecosystem",
".",
"\""
] |
finerord62 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Startup
leaders
are
also
concerned
about
the
time
it
would
take
for
the
area
to
be
redeveloped
from
an
abandoned
coal
-
fired
power
station
.
Answer: | Startup:O
leaders:O
are:O
also:O
concerned:O
about:O
the:O
time:O
it:O
would:O
take:O
for:O
the:O
area:O
to:O
be:O
redeveloped:O
from:O
an:O
abandoned:O
coal:O
-:O
fired:O
power:O
station:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Startup",
"leaders",
"are",
"also",
"concerned",
"about",
"the",
"time",
"it",
"would",
"take",
"for",
"the",
"area",
"to",
"be",
"redeveloped",
"from",
"an",
"abandoned",
"coal",
"-",
"fired",
"power",
"station",
"."
] |
finerord63 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: "
With
the
government
's
proposal
,
the
tech
community
would
become
displaced
until
well
beyond
2020
,
a
millennium
in
technology
years
,
"
Atlassian
said
.
Answer: | ":O
With:O
the:O
government:O
's:O
proposal:O
,:O
the:O
tech:O
community:O
would:O
become:O
displaced:O
until:O
well:O
beyond:O
2020:O
,:O
a:O
millennium:O
in:O
technology:O
years:O
,:O
":O
Atlassian:B-ORG
said:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O"
] | [
"\"",
"With",
"the",
"government",
"'s",
"proposal",
",",
"the",
"tech",
"community",
"would",
"become",
"displaced",
"until",
"well",
"beyond",
"2020",
",",
"a",
"millennium",
"in",
"technology",
"years",
",",
"\"",
"Atlassian",
"said",
"."
] |
finerord64 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: However
the
federal
Assistant
Minister
for
Innovation
Wyatt
Roy
dismissed
quibbles
about
location
,
and
said
the
launch
of
a
Sydney
tech
district
would
inspire
other
states
to
create
their
own
hotspots
.
Answer: | However:O
the:O
federal:O
Assistant:O
Minister:O
for:O
Innovation:O
Wyatt:B-PER
Roy:I-PER
dismissed:O
quibbles:O
about:O
location:O
,:O
and:O
said:O
the:O
launch:O
of:O
a:O
Sydney:B-LOC
tech:O
district:O
would:O
inspire:O
other:O
states:O
to:O
create:O
their:O
own:O
hotspots:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-PER",
"I-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
"the",
"federal",
"Assistant",
"Minister",
"for",
"Innovation",
"Wyatt",
"Roy",
"dismissed",
"quibbles",
"about",
"location",
",",
"and",
"said",
"the",
"launch",
"of",
"a",
"Sydney",
"tech",
"district",
"would",
"inspire",
"other",
"states",
"to",
"create",
"their",
"own",
"hotspots",
"."
] |
finerord65 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: "
I
think
it
's
very
important
that
we
do
this
wherever
possible
,
and
if
you
look
globally
you
do
n't
just
see
a
single
hub
of
innovation
you
see
several
of
them
like
in
the
US
and
Israel
,
"
he
told
AAP
.
Answer: | ":O
I:O
think:O
it:O
's:O
very:O
important:O
that:O
we:O
do:O
this:O
wherever:O
possible:O
,:O
and:O
if:O
you:O
look:O
globally:O
you:O
do:O
n't:O
just:O
see:O
a:O
single:O
hub:O
of:O
innovation:O
you:O
see:O
several:O
of:O
them:O
like:O
in:O
the:O
US:B-LOC
and:O
Israel:B-LOC
,:O
":O
he:O
told:O
AAP:B-ORG
.:I-ORG | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG"
] | [
"\"",
"I",
"think",
"it",
"'s",
"very",
"important",
"that",
"we",
"do",
"this",
"wherever",
"possible",
",",
"and",
"if",
"you",
"look",
"globally",
"you",
"do",
"n't",
"just",
"see",
"a",
"single",
"hub",
"of",
"innovation",
"you",
"see",
"several",
"of",
"them",
"like",
"in",
"the",
"US",
"and",
"Israel",
",",
"\"",
"he",
"told",
"AAP",
"."
] |
finerord66 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Mr
Roy
said
the
site
would
need
cornerstone
tenants
like
Google
Australia
or
the
CSIRO
to
anchor
the
hub
and
attract
local
and
international
businesses
.
Answer: | Mr:O
Roy:B-PER
said:O
the:O
site:O
would:O
need:O
cornerstone:O
tenants:O
like:O
Google:B-ORG
Australia:I-ORG
or:O
the:O
CSIRO:B-ORG
to:O
anchor:O
the:O
hub:O
and:O
attract:O
local:O
and:O
international:O
businesses:O
.:O | [
"O",
"B-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Mr",
"Roy",
"said",
"the",
"site",
"would",
"need",
"cornerstone",
"tenants",
"like",
"Google",
"Australia",
"or",
"the",
"CSIRO",
"to",
"anchor",
"the",
"hub",
"and",
"attract",
"local",
"and",
"international",
"businesses",
"."
] |
finerord67 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Founder
of
startup
incubator
BlueChilli
,
Sebastien
Eckersley
-
Maslin
,
shared
Atlassian
's
concerns
about
steep
rents
.
Answer: | Founder:O
of:O
startup:O
incubator:O
BlueChilli:B-PER
,:O
Sebastien:B-PER
Eckersley:I-PER
-:I-PER
Maslin:I-PER
,:O
shared:O
Atlassian:B-ORG
's:O
concerns:O
about:O
steep:O
rents:O
.:O | [
"O",
"O",
"O",
"O",
"B-PER",
"O",
"B-PER",
"I-PER",
"I-PER",
"I-PER",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Founder",
"of",
"startup",
"incubator",
"BlueChilli",
",",
"Sebastien",
"Eckersley",
"-",
"Maslin",
",",
"shared",
"Atlassian",
"'s",
"concerns",
"about",
"steep",
"rents",
"."
] |
finerord68 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: "
Putting
a
lot
of
money
into
a
development
centre
will
only
benefit
startups
if
the
rent
is
subsidised
in
some
way
,
"
he
said
.
Answer: | ":O
Putting:O
a:O
lot:O
of:O
money:O
into:O
a:O
development:O
centre:O
will:O
only:O
benefit:O
startups:O
if:O
the:O
rent:O
is:O
subsidised:O
in:O
some:O
way:O
,:O
":O
he:O
said:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"\"",
"Putting",
"a",
"lot",
"of",
"money",
"into",
"a",
"development",
"centre",
"will",
"only",
"benefit",
"startups",
"if",
"the",
"rent",
"is",
"subsidised",
"in",
"some",
"way",
",",
"\"",
"he",
"said",
"."
] |
finerord69 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: He
added
that
governments
should
encourage
large
multinational
companies
like
Google
to
set
up
research
and
development
centres
to
attract
industry
players
.
Answer: | He:O
added:O
that:O
governments:O
should:O
encourage:O
large:O
multinational:O
companies:O
like:O
Google:B-ORG
to:O
set:O
up:O
research:O
and:O
development:O
centres:O
to:O
attract:O
industry:O
players:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"He",
"added",
"that",
"governments",
"should",
"encourage",
"large",
"multinational",
"companies",
"like",
"Google",
"to",
"set",
"up",
"research",
"and",
"development",
"centres",
"to",
"attract",
"industry",
"players",
"."
] |
finerord70 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: @
YahooNZBusiness
on
Twitter
,
become
a
fan
on
Facebook
Sydney
to
get
tech
city
on
the
harbour
AAP
"
(
It
could
be
)
a
place
where
global
giants
of
tech
and
innovation
work
with
startup
entrepreneurs
,
business
incubators
…
Answer: | @:O
YahooNZBusiness:B-ORG
on:O
Twitter:B-ORG
,:O
become:O
a:O
fan:O
on:O
Facebook:B-ORG
Sydney:I-ORG
to:O
get:O
tech:O
city:O
on:O
the:O
harbour:O
AAP:B-ORG
":O
(:O
It:O
could:O
be:O
):O
a:O
place:O
where:O
global:O
giants:O
of:O
tech:O
and:O
innovation:O
work:O
with:O
startup:O
entrepreneurs:O
,:O
business:O
incubators:O
…:O | [
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"@",
"YahooNZBusiness",
"on",
"Twitter",
",",
"become",
"a",
"fan",
"on",
"Facebook",
"Sydney",
"to",
"get",
"tech",
"city",
"on",
"the",
"harbour",
"AAP",
"\"",
"(",
"It",
"could",
"be",
")",
"a",
"place",
"where",
"global",
"giants",
"of",
"tech",
"and",
"innovation",
"work",
"with",
"startup",
"entrepreneurs",
",",
"business",
"incubators",
"…"
] |
finerord71 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Is
General
Motors
Headed
for
a
Crash
in
China
?
Answer: | Is:O
General:B-ORG
Motors:I-ORG
Headed:O
for:O
a:O
Crash:O
in:O
China:B-LOC
?:O | [
"O",
"B-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O"
] | [
"Is",
"General",
"Motors",
"Headed",
"for",
"a",
"Crash",
"in",
"China",
"?"
] |
finerord72 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Sales
are
slowing
in
the
world
's
largest
auto
market
.
Answer: | Sales:O
are:O
slowing:O
in:O
the:O
world:O
's:O
largest:O
auto:O
market:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Sales",
"are",
"slowing",
"in",
"the",
"world",
"'s",
"largest",
"auto",
"market",
"."
] |
finerord73 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: What
does
that
mean
for
America
's
largest
automaker
?
Answer: | What:O
does:O
that:O
mean:O
for:O
America:B-LOC
's:O
largest:O
automaker:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O"
] | [
"What",
"does",
"that",
"mean",
"for",
"America",
"'s",
"largest",
"automaker",
"?"
] |
finerord74 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: John
Rosevear
TMFMarlowe
Jul
20
,
2015
at
7:07PM
GM
does
n't
sell
the
new
Buick
Envision
SUV
in
the
U.S
.
--
at
least
not
yet
.
Answer: | John:B-PER
Rosevear:I-PER
TMFMarlowe:B-ORG
Jul:O
20:O
,:O
2015:O
at:O
7:07PM:O
GM:B-ORG
does:O
n't:O
sell:O
the:O
new:O
Buick:O
Envision:O
SUV:O
in:O
the:O
U.S:B-LOC
.:I-LOC
--:O
at:O
least:O
not:O
yet:O
.:O | [
"B-PER",
"I-PER",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"John",
"Rosevear",
"TMFMarlowe",
"Jul",
"20",
",",
"2015",
"at",
"7:07PM",
"GM",
"does",
"n't",
"sell",
"the",
"new",
"Buick",
"Envision",
"SUV",
"in",
"the",
"U.S",
".",
"--",
"at",
"least",
"not",
"yet",
"."
] |
finerord75 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
it
's
racking
up
big
sales
numbers
in
China
,
where
SUVs
are
helping
GM
gain
ground
in
a
very
tough
market
.
Answer: | But:O
it:O
's:O
racking:O
up:O
big:O
sales:O
numbers:O
in:O
China:B-LOC
,:O
where:O
SUVs:O
are:O
helping:O
GM:B-ORG
gain:O
ground:O
in:O
a:O
very:O
tough:O
market:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"it",
"'s",
"racking",
"up",
"big",
"sales",
"numbers",
"in",
"China",
",",
"where",
"SUVs",
"are",
"helping",
"GM",
"gain",
"ground",
"in",
"a",
"very",
"tough",
"market",
"."
] |
finerord76 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Image
source
:
General
Motors
.
Answer: | Image:O
source:O
::O
General:B-ORG
Motors:I-ORG
.:O | [
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O"
] | [
"Image",
"source",
":",
"General",
"Motors",
"."
] |
finerord77 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Is
the
Chinese
auto
boom
headed
for
a
bust
?
Answer: | Is:O
the:O
Chinese:O
auto:O
boom:O
headed:O
for:O
a:O
bust:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Is",
"the",
"Chinese",
"auto",
"boom",
"headed",
"for",
"a",
"bust",
"?"
] |
finerord78 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Mighty
Volkswagen
Group
(
NASDAQ
Other
:
VLKAY
)
reported
that
its
sales
in
China
fell
almost
4
%
in
the
first
six
months
of
2015
.
Answer: | Mighty:B-ORG
Volkswagen:I-ORG
Group:I-ORG
(:O
NASDAQ:B-ORG
Other:O
::O
VLKAY:B-ORG
):O
reported:O
that:O
its:O
sales:O
in:O
China:B-LOC
fell:O
almost:O
4:O
%:O
in:O
the:O
first:O
six:O
months:O
of:O
2015:O
.:O | [
"B-ORG",
"I-ORG",
"I-ORG",
"O",
"B-ORG",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Mighty",
"Volkswagen",
"Group",
"(",
"NASDAQ",
"Other",
":",
"VLKAY",
")",
"reported",
"that",
"its",
"sales",
"in",
"China",
"fell",
"almost",
"4",
"%",
"in",
"the",
"first",
"six",
"months",
"of",
"2015",
"."
] |
finerord79 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Will
General
Motors
(
NYSE
:
GM
)
be
next
?
Answer: | Will:O
General:B-ORG
Motors:I-ORG
(:O
NYSE:B-ORG
::O
GM:B-ORG
):O
be:O
next:O
?:O | [
"O",
"B-ORG",
"I-ORG",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O"
] | [
"Will",
"General",
"Motors",
"(",
"NYSE",
":",
"GM",
")",
"be",
"next",
"?"
] |
finerord80 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
new
-
car
market
in
China
has
become
the
world
's
largest
.
Answer: | The:O
new:O
-:O
car:O
market:O
in:O
China:B-LOC
has:O
become:O
the:O
world:O
's:O
largest:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"new",
"-",
"car",
"market",
"in",
"China",
"has",
"become",
"the",
"world",
"'s",
"largest",
"."
] |
finerord81 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
in
recent
months
,
slowing
economic
growth
,
new
limits
on
car
ownership
in
certain
cities
,
and
volatility
in
China
's
stock
markets
have
kept
buyers
away
from
dealers
.
Answer: | But:O
in:O
recent:O
months:O
,:O
slowing:O
economic:O
growth:O
,:O
new:O
limits:O
on:O
car:O
ownership:O
in:O
certain:O
cities:O
,:O
and:O
volatility:O
in:O
China:B-LOC
's:O
stock:O
markets:O
have:O
kept:O
buyers:O
away:O
from:O
dealers:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"in",
"recent",
"months",
",",
"slowing",
"economic",
"growth",
",",
"new",
"limits",
"on",
"car",
"ownership",
"in",
"certain",
"cities",
",",
"and",
"volatility",
"in",
"China",
"'s",
"stock",
"markets",
"have",
"kept",
"buyers",
"away",
"from",
"dealers",
"."
] |
finerord82 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: VW
and
GM
are
the
two
biggest
players
in
China
's
auto
market
.
Answer: | VW:B-ORG
and:O
GM:B-ORG
are:O
the:O
two:O
biggest:O
players:O
in:O
China:B-LOC
's:O
auto:O
market:O
.:O | [
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O"
] | [
"VW",
"and",
"GM",
"are",
"the",
"two",
"biggest",
"players",
"in",
"China",
"'s",
"auto",
"market",
"."
] |
finerord83 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Nowadays
,
GM
sells
more
vehicles
in
China
than
it
does
anywhere
else
,
even
in
the
U.S.
Answer: | Nowadays:O
,:O
GM:B-ORG
sells:O
more:O
vehicles:O
in:O
China:B-LOC
than:O
it:O
does:O
anywhere:O
else:O
,:O
even:O
in:O
the:O
U.S.:O | [
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Nowadays",
",",
"GM",
"sells",
"more",
"vehicles",
"in",
"China",
"than",
"it",
"does",
"anywhere",
"else",
",",
"even",
"in",
"the",
"U.S."
] |
finerord84 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Is
VW
's
sales
decline
a
warning
for
GM
shareholders
?
Answer: | Is:O
VW:B-ORG
's:O
sales:O
decline:O
a:O
warning:O
for:O
GM:B-ORG
shareholders:O
?:O | [
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O"
] | [
"Is",
"VW",
"'s",
"sales",
"decline",
"a",
"warning",
"for",
"GM",
"shareholders",
"?"
] |
finerord85 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: GM
's
SUVs
are
keeping
it
going
in
China
,
for
now
All
of
the
automakers
doing
business
in
China
have
felt
the
impact
of
the
slowdown
to
some
degree
.
Answer: | GM:B-ORG
's:O
SUVs:O
are:O
keeping:O
it:O
going:O
in:O
China:B-LOC
,:O
for:O
now:O
All:O
of:O
the:O
automakers:O
doing:O
business:O
in:O
China:B-LOC
have:O
felt:O
the:O
impact:O
of:O
the:O
slowdown:O
to:O
some:O
degree:O
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"GM",
"'s",
"SUVs",
"are",
"keeping",
"it",
"going",
"in",
"China",
",",
"for",
"now",
"All",
"of",
"the",
"automakers",
"doing",
"business",
"in",
"China",
"have",
"felt",
"the",
"impact",
"of",
"the",
"slowdown",
"to",
"some",
"degree",
"."
] |
finerord86 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
so
far
,
at
least
,
GM
is
faring
better
than
Volkswagen
and
some
of
its
other
rivals
.
Answer: | But:O
so:O
far:O
,:O
at:O
least:O
,:O
GM:B-ORG
is:O
faring:O
better:O
than:O
Volkswagen:B-ORG
and:O
some:O
of:O
its:O
other:O
rivals:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"so",
"far",
",",
"at",
"least",
",",
"GM",
"is",
"faring",
"better",
"than",
"Volkswagen",
"and",
"some",
"of",
"its",
"other",
"rivals",
"."
] |
finerord87 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: GM
said
it
had
"
record
"
sales
in
China
during
the
first
half
of
2015
,
with
total
sales
up
4.4
%
from
a
very
good
result
last
year
.
Answer: | GM:B-ORG
said:O
it:O
had:O
":O
record:O
":O
sales:O
in:O
China:B-LOC
during:O
the:O
first:O
half:O
of:O
2015:O
,:O
with:O
total:O
sales:O
up:O
4.4:O
%:O
from:O
a:O
very:O
good:O
result:O
last:O
year:O
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"GM",
"said",
"it",
"had",
"\"",
"record",
"\"",
"sales",
"in",
"China",
"during",
"the",
"first",
"half",
"of",
"2015",
",",
"with",
"total",
"sales",
"up",
"4.4",
"%",
"from",
"a",
"very",
"good",
"result",
"last",
"year",
"."
] |
finerord88 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
GM
may
have
something
going
for
it
that
VW
does
n't
:
SUVs
.
Answer: | But:O
GM:B-ORG
may:O
have:O
something:O
going:O
for:O
it:O
that:O
VW:B-ORG
does:O
n't:O
::O
SUVs:O
.:O | [
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"GM",
"may",
"have",
"something",
"going",
"for",
"it",
"that",
"VW",
"does",
"n't",
":",
"SUVs",
"."
] |
finerord89 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: It
might
be
surprising
to
learn
that
General
Motors
--
of
all
companies
--
was
late
to
respond
to
the
booming
demand
for
SUVs
in
China
.
Answer: | It:O
might:O
be:O
surprising:O
to:O
learn:O
that:O
General:B-ORG
Motors:I-ORG
--:O
of:O
all:O
companies:O
--:O
was:O
late:O
to:O
respond:O
to:O
the:O
booming:O
demand:O
for:O
SUVs:O
in:O
China:B-LOC
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O"
] | [
"It",
"might",
"be",
"surprising",
"to",
"learn",
"that",
"General",
"Motors",
"--",
"of",
"all",
"companies",
"--",
"was",
"late",
"to",
"respond",
"to",
"the",
"booming",
"demand",
"for",
"SUVs",
"in",
"China",
"."
] |
finerord90 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Chinese
buyers
started
turning
toward
SUVs
a
few
years
ago
,
and
GM
's
Chinese
dealers
had
very
little
to
offer
them
at
the
time
.
Answer: | Chinese:O
buyers:O
started:O
turning:O
toward:O
SUVs:O
a:O
few:O
years:O
ago:O
,:O
and:O
GM:B-ORG
's:O
Chinese:O
dealers:O
had:O
very:O
little:O
to:O
offer:O
them:O
at:O
the:O
time:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Chinese",
"buyers",
"started",
"turning",
"toward",
"SUVs",
"a",
"few",
"years",
"ago",
",",
"and",
"GM",
"'s",
"Chinese",
"dealers",
"had",
"very",
"little",
"to",
"offer",
"them",
"at",
"the",
"time",
"."
] |
finerord91 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
that
has
changed
recently
,
in
a
big
way
.
Answer: | But:O
that:O
has:O
changed:O
recently:O
,:O
in:O
a:O
big:O
way:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"that",
"has",
"changed",
"recently",
",",
"in",
"a",
"big",
"way",
"."
] |
finerord92 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: GM
said
that
retail
sales
of
its
SUV
models
rose
almost
83
%
in
the
first
half
of
the
year
,
led
by
the
Buick
Envision
--
a
model
that
is
n't
(
yet
,
at
least
)
sold
in
the
United
States
.
Answer: | GM:B-ORG
said:O
that:O
retail:O
sales:O
of:O
its:O
SUV:O
models:O
rose:O
almost:O
83:O
%:O
in:O
the:O
first:O
half:O
of:O
the:O
year:O
,:O
led:O
by:O
the:O
Buick:O
Envision:O
--:O
a:O
model:O
that:O
is:O
n't:O
(:O
yet:O
,:O
at:O
least:O
):O
sold:O
in:O
the:O
United:B-LOC
States:I-LOC
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O"
] | [
"GM",
"said",
"that",
"retail",
"sales",
"of",
"its",
"SUV",
"models",
"rose",
"almost",
"83",
"%",
"in",
"the",
"first",
"half",
"of",
"the",
"year",
",",
"led",
"by",
"the",
"Buick",
"Envision",
"--",
"a",
"model",
"that",
"is",
"n't",
"(",
"yet",
",",
"at",
"least",
")",
"sold",
"in",
"the",
"United",
"States",
"."
] |
finerord93 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
Envision
is
a
midsize
crossover
SUV
that
slots
between
the
two
Buick
SUVs
that
are
familiar
to
Americans
:
the
small
Encore
and
the
big
Enclave
.
Answer: | The:O
Envision:O
is:O
a:O
midsize:O
crossover:O
SUV:O
that:O
slots:O
between:O
the:O
two:O
Buick:O
SUVs:O
that:O
are:O
familiar:O
to:O
Americans:O
::O
the:O
small:O
Encore:O
and:O
the:O
big:O
Enclave:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"Envision",
"is",
"a",
"midsize",
"crossover",
"SUV",
"that",
"slots",
"between",
"the",
"two",
"Buick",
"SUVs",
"that",
"are",
"familiar",
"to",
"Americans",
":",
"the",
"small",
"Encore",
"and",
"the",
"big",
"Enclave",
"."
] |
finerord94 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Both
of
those
are
also
sold
in
China
,
and
demand
for
the
three
Buick
crossovers
as
a
group
more
than
doubled
in
the
first
half
of
2015
,
with
almost
100,000
sold
.
Answer: | Both:O
of:O
those:O
are:O
also:O
sold:O
in:O
China:B-LOC
,:O
and:O
demand:O
for:O
the:O
three:O
Buick:O
crossovers:O
as:O
a:O
group:O
more:O
than:O
doubled:O
in:O
the:O
first:O
half:O
of:O
2015:O
,:O
with:O
almost:O
100,000:O
sold:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Both",
"of",
"those",
"are",
"also",
"sold",
"in",
"China",
",",
"and",
"demand",
"for",
"the",
"three",
"Buick",
"crossovers",
"as",
"a",
"group",
"more",
"than",
"doubled",
"in",
"the",
"first",
"half",
"of",
"2015",
",",
"with",
"almost",
"100,000",
"sold",
"."
] |
finerord95 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: But
will
that
be
enough
to
keep
GM
's
growth
going
if
the
Chinese
market
continues
to
sag
?
Answer: | But:O
will:O
that:O
be:O
enough:O
to:O
keep:O
GM:B-ORG
's:O
growth:O
going:O
if:O
the:O
Chinese:O
market:O
continues:O
to:O
sag:O
?:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"But",
"will",
"that",
"be",
"enough",
"to",
"keep",
"GM",
"'s",
"growth",
"going",
"if",
"the",
"Chinese",
"market",
"continues",
"to",
"sag",
"?"
] |
finerord96 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: The
slowdown
is
hitting
all
of
the
key
players
in
China
Answer: | The:O
slowdown:O
is:O
hitting:O
all:O
of:O
the:O
key:O
players:O
in:O
China:B-LOC | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC"
] | [
"The",
"slowdown",
"is",
"hitting",
"all",
"of",
"the",
"key",
"players",
"in",
"China"
] |
finerord97 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: If
not
,
GM
will
certainly
have
a
lot
of
company
.
Answer: | If:O
not:O
,:O
GM:B-ORG
will:O
certainly:O
have:O
a:O
lot:O
of:O
company:O
.:O | [
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"If",
"not",
",",
"GM",
"will",
"certainly",
"have",
"a",
"lot",
"of",
"company",
"."
] |
finerord98 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Ford
(
NYSE
:
F
)
has
posted
huge
growth
in
China
over
the
last
few
years
,
but
it
managed
just
a
tiny
0.1
%
gain
in
the
first
half
of
the
year
.
Answer: | Ford:O
(:O
NYSE:B-ORG
::O
F:B-ORG
):O
has:O
posted:O
huge:O
growth:O
in:O
China:B-LOC
over:O
the:O
last:O
few:O
years:O
,:O
but:O
it:O
managed:O
just:O
a:O
tiny:O
0.1:O
%:O
gain:O
in:O
the:O
first:O
half:O
of:O
the:O
year:O
.:O | [
"O",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Ford",
"(",
"NYSE",
":",
"F",
")",
"has",
"posted",
"huge",
"growth",
"in",
"China",
"over",
"the",
"last",
"few",
"years",
",",
"but",
"it",
"managed",
"just",
"a",
"tiny",
"0.1",
"%",
"gain",
"in",
"the",
"first",
"half",
"of",
"the",
"year",
"."
] |
finerord99 | In the list of tokens, identify 'Person', 'Location', and 'Organisation' and label each accordingly. If the entity spans multiple tokens, use the prefix B-PER, B-LOC, or B-ORG for the first token, and I-PER, I-LOC, or I-ORG for the subsequent tokens of that entity. The beginning of each separate entity should always be labeled with a B-PER, B-LOC, or B-ORG prefix. If the token does not fit into any of the three named categories, or is not a named entity, label it as 'O'. Each line should contain one token and its corresponding label, separated by a colon. Do not combine tokens on your own. The format for each line should be: 'token:label'.
Text: Toyota
,
Honda
,
and
Nissan
all
did
somewhat
better
,
but
all
were
hurt
by
anti-Japanese
sentiment
that
was
more
prevalent
in
China
a
year
ago
that
made
the
year
-
over
-
year
comparison
look
especially
favorable
.
Answer: | Toyota:B-ORG
,:O
Honda:B-ORG
,:O
and:O
Nissan:B-ORG
all:O
did:O
somewhat:O
better:O
,:O
but:O
all:O
were:O
hurt:O
by:O
anti-Japanese:O
sentiment:O
that:O
was:O
more:O
prevalent:O
in:O
China:B-LOC
a:O
year:O
ago:O
that:O
made:O
the:O
year:O
-:O
over:O
-:O
year:O
comparison:O
look:O
especially:O
favorable:O
.:O | [
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Toyota",
",",
"Honda",
",",
"and",
"Nissan",
"all",
"did",
"somewhat",
"better",
",",
"but",
"all",
"were",
"hurt",
"by",
"anti-Japanese",
"sentiment",
"that",
"was",
"more",
"prevalent",
"in",
"China",
"a",
"year",
"ago",
"that",
"made",
"the",
"year",
"-",
"over",
"-",
"year",
"comparison",
"look",
"especially",
"favorable",
"."
] |
End of preview. Expand
in Dataset Viewer.
Dataset Card for FinBen-FiNER-ORD
Dataset Summary
FinBen-FiNER-ORD is a financial named entity recognition (NER) dataset adapted from FiNER-ORD (Shah et al., 2023b). The dataset is designed for training and evaluating large language models (LLMs) on financial text entity recognition tasks. The dataset includes necessary label columns and instructions to enhance its usability for LLM-based training and evaluation.
Supported Tasks and Leaderboards
- Task: Named Entity Recognition (NER)
- Evaluation Metric: Entity F1 Score
- Test Size: 1080 instances
Languages
- English
Dataset Structure
Data Instances
Each instance consists of a list of tokens along with their corresponding entity labels. The annotation follows the BIO tagging format:
- B-PER, B-LOC, B-ORG: Indicates the beginning of an entity (Person, Location, Organization).
- I-PER, I-LOC, I-ORG: Indicates the continuation of an entity.
- O: Indicates a token that does not belong to any named entity category.
Data Fields
- id: A unique identifier for each data instance.
- query: The input text that the model processes.
- answer: The expected response or annotation.
- label: The sequence of labels for each token.
- token: The tokenized version of the query text.
Data Splits
The dataset is split into:
- Test: 1080 instances
Dataset Creation
Curation Rationale
The dataset is adapted from FiNER-ORD (Shah et al., 2023b) to improve its suitability for LLM-based NER tasks by adding instruction and label columns for better training and evaluation.
Source Data
Initial Data Collection and Normalization
The dataset originates from financial documents and articles containing named entities relevant to financial contexts.
Who are the source language producers?
Financial analysts, researchers, and automated data extraction systems.
Annotations
Annotation Process
Annotations follow the BIO tagging scheme, where entities are labeled manually and reviewed for accuracy.
Who are the annotators?
Trained annotators with expertise in financial document analysis.
Personal and Sensitive Information
No personally identifiable information (PII) is included.
Considerations for Using the Data
Social Impact of Dataset
This dataset enhances financial NLP capabilities, allowing more accurate extraction of named entities in financial texts.
Discussion of Biases
Potential biases may exist due to:
- Overrepresentation of specific financial sectors.
- Linguistic biases in the original dataset.
Other Known Limitations
- May require domain-specific fine-tuning.
- Lacks multilingual support.
Additional Information
Dataset Curators
- The Fin AI Community
Licensing Information
- License: CC BY-NC 4.0
Citation Information
@article{shah2023finer,
title={FiNER: Financial Named Entity Recognition Dataset and Weak-Supervision Model},
author={Shah, Agam and Vithani, Ruchit and Gullapalli, Abhinav and Chava, Sudheer},
journal={arXiv preprint arXiv:2302.11157},
year={2023}
}
Adapted Version (FinBen-FiNER-ORD):
@article{xie2024finben,
title={FinBen: A Holistic Financial Benchmark for Large Language Models},
author={Xie, Qianqian and others},
journal={arXiv preprint arXiv:2402.12659},
year={2024}
}
- Downloads last month
- 10
Homepage:
huggingface.co
Repository:
huggingface.co
Paper:
FinBen: A Holistic Financial Benchmark for Large Language Models
Leaderboard:
huggingface.co
Size of downloaded dataset files:
357 kB
Size of the auto-converted Parquet files:
357 kB
Number of rows:
1,075