id
stringlengths 9
12
| query
stringlengths 665
1.43k
| answer
stringlengths 3
1.21k
| label
sequence | token
sequence |
|---|---|---|---|---|
finerord200 | 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
United
States
contracting
in
the
first
quarter
and
some
underperformance
within
Asia
and
the
Pacific
,
growth
forecasts
for
developing
Asia
are
adjusted
down
,
'
the
report
said
.
Answer: | ':O
With:O
the:O
United:B-LOC
States:I-LOC
contracting:O
in:O
the:O
first:O
quarter:O
and:O
some:O
underperformance:O
within:O
Asia:B-LOC
and:O
the:O
Pacific:B-LOC
,:O
growth:O
forecasts:O
for:O
developing:O
Asia:B-LOC
are:O
adjusted:O
down:O
,:O
':O
the:O
report:O
said:O
.:O | [
"O",
"O",
"O",
"B-LOC",
"I-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"'",
"With",
"the",
"United",
"States",
"contracting",
"in",
"the",
"first",
"quarter",
"and",
"some",
"underperformance",
"within",
"Asia",
"and",
"the",
"Pacific",
",",
"growth",
"forecasts",
"for",
"developing",
"Asia",
"are",
"adjusted",
"down",
",",
"'",
"the",
"report",
"said",
"."
] |
finerord201 | 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: '
Slower
growth
in
China
is
likely
to
have
a
noticeable
effect
on
the
rest
of
Asia
given
its
size
and
its
close
links
with
other
countries
in
the
region
through
regional
and
global
value
chains
,
'
ADB
chief
economist
Shang
Jin-Wei
added
.
Answer: | ':O
Slower:O
growth:O
in:O
China:B-LOC
is:O
likely:O
to:O
have:O
a:O
noticeable:O
effect:O
on:O
the:O
rest:O
of:O
Asia:B-LOC
given:O
its:O
size:O
and:O
its:O
close:O
links:O
with:O
other:O
countries:O
in:O
the:O
region:O
through:O
regional:O
and:O
global:O
value:O
chains:O
,:O
':O
ADB:B-ORG
chief:O
economist:O
Shang:B-PER
Jin-Wei:I-PER
added:O
.:O | [
"O",
"O",
"O",
"O",
"B-LOC",
"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",
"B-ORG",
"O",
"O",
"B-PER",
"I-PER",
"O",
"O"
] | [
"'",
"Slower",
"growth",
"in",
"China",
"is",
"likely",
"to",
"have",
"a",
"noticeable",
"effect",
"on",
"the",
"rest",
"of",
"Asia",
"given",
"its",
"size",
"and",
"its",
"close",
"links",
"with",
"other",
"countries",
"in",
"the",
"region",
"through",
"regional",
"and",
"global",
"value",
"chains",
",",
"'",
"ADB",
"chief",
"economist",
"Shang",
"Jin-Wei",
"added",
"."
] |
finerord202 | 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: Full
-
year
growth
in
China
is
now
estimated
at
7
per
cent
in
2015
,
down
from
7.2
per
cent
previously
after
a
slow
first
half
.
Answer: | Full:O
-:O
year:O
growth:O
in:O
China:B-LOC
is:O
now:O
estimated:O
at:O
7:O
per:O
cent:O
in:O
2015:O
,:O
down:O
from:O
7.2:O
per:O
cent:O
previously:O
after:O
a:O
slow:O
first:O
half: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"
] | [
"Full",
"-",
"year",
"growth",
"in",
"China",
"is",
"now",
"estimated",
"at",
"7",
"per",
"cent",
"in",
"2015",
",",
"down",
"from",
"7.2",
"per",
"cent",
"previously",
"after",
"a",
"slow",
"first",
"half",
"."
] |
finerord203 | 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: Growth
would
ease
further
to
6.8
per
cent
next
year
,
the
report
said
.
Answer: | Growth:O
would:O
ease:O
further:O
to:O
6.8:O
per:O
cent:O
next:O
year:O
,:O
the:O
report:O
said:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Growth",
"would",
"ease",
"further",
"to",
"6.8",
"per",
"cent",
"next",
"year",
",",
"the",
"report",
"said",
"."
] |
finerord204 | 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
bank
revised
down
its
projection
for
inflation
in
the
region
to
2.4
per
cent
in
2015
,
from
an
earlier
estimate
of
2.6
per
cent
amid
softness
in
fuel
prices
and
subdued
food
costs
.
Answer: | The:O
bank:O
revised:O
down:O
its:O
projection:O
for:O
inflation:O
in:O
the:O
region:O
to:O
2.4:O
per:O
cent:O
in:O
2015:O
,:O
from:O
an:O
earlier:O
estimate:O
of:O
2.6:O
per:O
cent:O
amid:O
softness:O
in:O
fuel:O
prices:O
and:O
subdued:O
food:O
costs:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"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",
"bank",
"revised",
"down",
"its",
"projection",
"for",
"inflation",
"in",
"the",
"region",
"to",
"2.4",
"per",
"cent",
"in",
"2015",
",",
"from",
"an",
"earlier",
"estimate",
"of",
"2.6",
"per",
"cent",
"amid",
"softness",
"in",
"fuel",
"prices",
"and",
"subdued",
"food",
"costs",
"."
] |
finerord205 | 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: '
Inflation
is
seen
at
3
per
cent
in
2016
,
unchanged
from
the
previous
forecast
,
'
it
added
.
Answer: | ':O
Inflation:O
is:O
seen:O
at:O
3:O
per:O
cent:O
in:O
2016:O
,:O
unchanged:O
from:O
the:O
previous:O
forecast:O
,:O
':O
it:O
added:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"'",
"Inflation",
"is",
"seen",
"at",
"3",
"per",
"cent",
"in",
"2016",
",",
"unchanged",
"from",
"the",
"previous",
"forecast",
",",
"'",
"it",
"added",
"."
] |
finerord206 | 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: Twitter
More
often
than
not
,
Android
OS
is
considered
as
less
secure
.
Answer: | Twitter:B-ORG
More:O
often:O
than:O
not:O
,:O
Android:O
OS:O
is:O
considered:O
as:O
less:O
secure:O
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Twitter",
"More",
"often",
"than",
"not",
",",
"Android",
"OS",
"is",
"considered",
"as",
"less",
"secure",
"."
] |
finerord207 | 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: Apple
’s
iOS
platform
is
relatively
free
of
such
issues
.
Answer: | Apple:B-ORG
’s:O
iOS:O
platform:O
is:O
relatively:O
free:O
of:O
such:O
issues:O
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Apple",
"’s",
"iOS",
"platform",
"is",
"relatively",
"free",
"of",
"such",
"issues",
"."
] |
finerord208 | 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
,
a
few
days
back
,
security
researchers
revealed
that
many
of
the
top
apps
on
the
Apple
App
store
were
infected
with
malware
.
Answer: | However:O
,:O
a:O
few:O
days:O
back:O
,:O
security:O
researchers:O
revealed:O
that:O
many:O
of:O
the:O
top:O
apps:O
on:O
the:O
Apple:O
App:O
store:O
were:O
infected:O
with:O
malware:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
",",
"a",
"few",
"days",
"back",
",",
"security",
"researchers",
"revealed",
"that",
"many",
"of",
"the",
"top",
"apps",
"on",
"the",
"Apple",
"App",
"store",
"were",
"infected",
"with",
"malware",
"."
] |
finerord209 | 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
it
’s
still
unclear
how
many
apps
in
total
were
affected
by
this
issue
,
now
the
company
has
removed
a
number
of
iOS
apps
that
were
believed
to
be
plagued
by
the
malware
.
Answer: | While:O
it:O
’s:O
still:O
unclear:O
how:O
many:O
apps:O
in:O
total:O
were:O
affected:O
by:O
this:O
issue:O
,:O
now:O
the:O
company:O
has:O
removed:O
a:O
number:O
of:O
iOS:O
apps:O
that:O
were:O
believed:O
to:O
be:O
plagued:O
by:O
the:O
malware:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"While",
"it",
"’s",
"still",
"unclear",
"how",
"many",
"apps",
"in",
"total",
"were",
"affected",
"by",
"this",
"issue",
",",
"now",
"the",
"company",
"has",
"removed",
"a",
"number",
"of",
"iOS",
"apps",
"that",
"were",
"believed",
"to",
"be",
"plagued",
"by",
"the",
"malware",
"."
] |
finerord210 | 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: Sponsored
Links
Palo
Alto
Answer: | Sponsored:O
Links:O
Palo:B-ORG
Alto:I-ORG | [
"O",
"O",
"B-ORG",
"I-ORG"
] | [
"Sponsored",
"Links",
"Palo",
"Alto"
] |
finerord211 | 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: Networks
,
the
firm
who
found
out
this
malware
said
that
there
were
around
39
apps
that
were
affected
by
malware
on
the
Apple
app
store
.
Answer: | Networks:I-ORG
,:O
the:O
firm:O
who:O
found:O
out:O
this:O
malware:O
said:O
that:O
there:O
were:O
around:O
39:O
apps:O
that:O
were:O
affected:O
by:O
malware:O
on:O
the:O
Apple:O
app:O
store:O
.:O | [
"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"
] | [
"Networks",
",",
"the",
"firm",
"who",
"found",
"out",
"this",
"malware",
"said",
"that",
"there",
"were",
"around",
"39",
"apps",
"that",
"were",
"affected",
"by",
"malware",
"on",
"the",
"Apple",
"app",
"store",
"."
] |
finerord212 | 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: Many
of
these
are
top
selling
apps
on
the
store
,
like
WeChat
,
Didi
Kuaidi
,
CamCard
,
Railway
12306
etc
.
Answer: | Many:O
of:O
these:O
are:O
top:O
selling:O
apps:O
on:O
the:O
store:O
,:O
like:O
WeChat:O
,:O
Didi:O
Kuaidi:O
,:O
CamCard:O
,:O
Railway:O
12306:O
etc:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Many",
"of",
"these",
"are",
"top",
"selling",
"apps",
"on",
"the",
"store",
",",
"like",
"WeChat",
",",
"Didi",
"Kuaidi",
",",
"CamCard",
",",
"Railway",
"12306",
"etc",
"."
] |
finerord213 | 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
security
firm
estimates
around
39
infected
apps
,
another
Chinese
security
research
company
claims
that
this
figure
may
be
much
greater
than
300
.
Answer: | While:O
the:O
security:O
firm:O
estimates:O
around:O
39:O
infected:O
apps:O
,:O
another:O
Chinese:O
security:O
research:O
company:O
claims:O
that:O
this:O
figure:O
may:O
be:O
much:O
greater:O
than:O
300:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"While",
"the",
"security",
"firm",
"estimates",
"around",
"39",
"infected",
"apps",
",",
"another",
"Chinese",
"security",
"research",
"company",
"claims",
"that",
"this",
"figure",
"may",
"be",
"much",
"greater",
"than",
"300",
"."
] |
finerord214 | 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: Apple
App
store
is
usually
found
to
be
much
more
secure
and
stable
as
compared
to
its
competitors
.
Answer: | Apple:O
App:O
store:O
is:O
usually:O
found:O
to:O
be:O
much:O
more:O
secure:O
and:O
stable:O
as:O
compared:O
to:O
its:O
competitors:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Apple",
"App",
"store",
"is",
"usually",
"found",
"to",
"be",
"much",
"more",
"secure",
"and",
"stable",
"as",
"compared",
"to",
"its",
"competitors",
"."
] |
finerord215 | 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: This
is
because
the
Cupertino
giant
makes
sure
that
each
and
every
app
that
gets
listed
on
the
store
has
to
pass
stringent
tests
.
Answer: | This:O
is:O
because:O
the:O
Cupertino:B-LOC
giant:O
makes:O
sure:O
that:O
each:O
and:O
every:O
app:O
that:O
gets:O
listed:O
on:O
the:O
store:O
has:O
to:O
pass:O
stringent:O
tests: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"
] | [
"This",
"is",
"because",
"the",
"Cupertino",
"giant",
"makes",
"sure",
"that",
"each",
"and",
"every",
"app",
"that",
"gets",
"listed",
"on",
"the",
"store",
"has",
"to",
"pass",
"stringent",
"tests",
"."
] |
finerord216 | 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: This
has
helped
the
company
maintain
its
impeccable
reputation
so
far
.
Answer: | This:O
has:O
helped:O
the:O
company:O
maintain:O
its:O
impeccable:O
reputation:O
so:O
far:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"This",
"has",
"helped",
"the",
"company",
"maintain",
"its",
"impeccable",
"reputation",
"so",
"far",
"."
] |
finerord217 | 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
,
it
looks
like
attackers
used
another
way
to
bypass
Apple
’s
security
measures
.
Answer: | However:O
,:O
it:O
looks:O
like:O
attackers:O
used:O
another:O
way:O
to:O
bypass:O
Apple:B-ORG
’s:O
security:O
measures:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O"
] | [
"However",
",",
"it",
"looks",
"like",
"attackers",
"used",
"another",
"way",
"to",
"bypass",
"Apple",
"’s",
"security",
"measures",
"."
] |
finerord218 | 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: They
released
an
infected
fake
version
of
the
Xcode
,
which
is
the
code
used
by
developers
to
build
apps
for
the
iOS
platform
.
Answer: | They:O
released:O
an:O
infected:O
fake:O
version:O
of:O
the:O
Xcode:O
,:O
which:O
is:O
the:O
code:O
used:O
by:O
developers:O
to:O
build:O
apps:O
for:O
the:O
iOS:O
platform:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"They",
"released",
"an",
"infected",
"fake",
"version",
"of",
"the",
"Xcode",
",",
"which",
"is",
"the",
"code",
"used",
"by",
"developers",
"to",
"build",
"apps",
"for",
"the",
"iOS",
"platform",
"."
] |
finerord219 | 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
is
said
that
the
fake
version
was
uploaded
on
a
Chinese
server
,
which
was
reportedly
faster
than
the
US
server
.
Answer: | It:O
is:O
said:O
that:O
the:O
fake:O
version:O
was:O
uploaded:O
on:O
a:O
Chinese:O
server:O
,:O
which:O
was:O
reportedly:O
faster:O
than:O
the:O
US:B-LOC
server: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"
] | [
"It",
"is",
"said",
"that",
"the",
"fake",
"version",
"was",
"uploaded",
"on",
"a",
"Chinese",
"server",
",",
"which",
"was",
"reportedly",
"faster",
"than",
"the",
"US",
"server",
"."
] |
finerord220 | 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
Apple
Website
is
much
slower
than
local
sites
like
Baidu
cloud
where
the
infected
software
was
uploaded
,
thanks
to
the
Great
Firewall
of
China
.
Answer: | The:O
Apple:B-ORG
Website:O
is:O
much:O
slower:O
than:O
local:O
sites:O
like:O
Baidu:O
cloud:O
where:O
the:O
infected:O
software:O
was:O
uploaded:O
,:O
thanks:O
to:O
the:O
Great:O
Firewall:O
of:O
China:B-LOC
.: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",
"B-LOC",
"O"
] | [
"The",
"Apple",
"Website",
"is",
"much",
"slower",
"than",
"local",
"sites",
"like",
"Baidu",
"cloud",
"where",
"the",
"infected",
"software",
"was",
"uploaded",
",",
"thanks",
"to",
"the",
"Great",
"Firewall",
"of",
"China",
"."
] |
finerord221 | 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: So
,
anyone
who
used
this
copy
created
infected
apps
.
Answer: | So:O
,:O
anyone:O
who:O
used:O
this:O
copy:O
created:O
infected:O
apps:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"So",
",",
"anyone",
"who",
"used",
"this",
"copy",
"created",
"infected",
"apps",
"."
] |
finerord222 | 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
infected
code
in
the
app
works
like
most
other
app
malwares
on
the
internet
.
Answer: | The:O
infected:O
code:O
in:O
the:O
app:O
works:O
like:O
most:O
other:O
app:O
malwares:O
on:O
the:O
internet:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"infected",
"code",
"in",
"the",
"app",
"works",
"like",
"most",
"other",
"app",
"malwares",
"on",
"the",
"internet",
"."
] |
finerord223 | 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
can
prompt
the
user
to
re-enter
the
username
and
password
via
fake
login
attempt
.
Answer: | It:O
can:O
prompt:O
the:O
user:O
to:O
re-enter:O
the:O
username:O
and:O
password:O
via:O
fake:O
login:O
attempt:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"can",
"prompt",
"the",
"user",
"to",
"re-enter",
"the",
"username",
"and",
"password",
"via",
"fake",
"login",
"attempt",
"."
] |
finerord224 | 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: Once
these
details
are
entered
,
it
can
then
be
sent
to
a
third
party
server
which
stores
these
data
.
Answer: | Once:O
these:O
details:O
are:O
entered:O
,:O
it:O
can:O
then:O
be:O
sent:O
to:O
a:O
third:O
party:O
server:O
which:O
stores:O
these:O
data:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Once",
"these",
"details",
"are",
"entered",
",",
"it",
"can",
"then",
"be",
"sent",
"to",
"a",
"third",
"party",
"server",
"which",
"stores",
"these",
"data",
"."
] |
finerord225 | 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: Other
possible
ways
to
access
details
include
accessing
the
user
’s
clipboard
.
Answer: | Other:O
possible:O
ways:O
to:O
access:O
details:O
include:O
accessing:O
the:O
user:O
’s:O
clipboard:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Other",
"possible",
"ways",
"to",
"access",
"details",
"include",
"accessing",
"the",
"user",
"’s",
"clipboard",
"."
] |
finerord226 | 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: This
can
turn
out
to
be
disastrous
for
many
users
who
make
use
of
password
managers
for
logging
into
their
accounts
.
Answer: | This:O
can:O
turn:O
out:O
to:O
be:O
disastrous:O
for:O
many:O
users:O
who:O
make:O
use:O
of:O
password:O
managers:O
for:O
logging:O
into:O
their:O
accounts:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"This",
"can",
"turn",
"out",
"to",
"be",
"disastrous",
"for",
"many",
"users",
"who",
"make",
"use",
"of",
"password",
"managers",
"for",
"logging",
"into",
"their",
"accounts",
"."
] |
finerord227 | 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: Apple
has
already
removed
all
of
the
known
infected
apps
from
the
Apple
app
store
.
Answer: | Apple:B-ORG
has:O
already:O
removed:O
all:O
of:O
the:O
known:O
infected:O
apps:O
from:O
the:O
Apple:O
app:O
store:O
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Apple",
"has",
"already",
"removed",
"all",
"of",
"the",
"known",
"infected",
"apps",
"from",
"the",
"Apple",
"app",
"store",
"."
] |
finerord228 | 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
is
advised
that
users
update
their
apps
to
the
latest
version
as
soon
as
possible
.
Answer: | It:O
is:O
advised:O
that:O
users:O
update:O
their:O
apps:O
to:O
the:O
latest:O
version:O
as:O
soon:O
as:O
possible:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"is",
"advised",
"that",
"users",
"update",
"their",
"apps",
"to",
"the",
"latest",
"version",
"as",
"soon",
"as",
"possible",
"."
] |
finerord229 | 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: TAGS
Answer: | TAGS:O | [
"O"
] | [
"TAGS"
] |
finerord230 | 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: Tip
:
Use
comma
(
,
)
to
separate
multiple
quotes
.
Answer: | Tip:O
::O
Use:O
comma:O
(:O
,:O
):O
to:O
separate:O
multiple:O
quotes:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Tip",
":",
"Use",
"comma",
"(",
",",
")",
"to",
"separate",
"multiple",
"quotes",
"."
] |
finerord231 | 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: Learn
more
...
Answer: | Learn:O
more:O
...:O | [
"O",
"O",
"O"
] | [
"Learn",
"more",
"..."
] |
finerord232 | 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: Mon
,
Jul
6
,
2015
,
14:45
BST
-
UK
Answer: | Mon:O
,:O
Jul:O
6:O
,:O
2015:O
,:O
14:45:O
BST:O
-:O
UK:B-LOC | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC"
] | [
"Mon",
",",
"Jul",
"6",
",",
"2015",
",",
"14:45",
"BST",
"-",
"UK"
] |
finerord233 | 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: Markets
close
in
1
hr
45
mins
Firms
cornered
by
watchdog
over
pension
freedom
blocks
By
Katie
Morley
|
Telegraph
–
12
minutes
ago
Print
Answer: | Markets:O
close:O
in:O
1:O
hr:O
45:O
mins:O
Firms:O
cornered:O
by:O
watchdog:O
over:O
pension:O
freedom:O
blocks:O
By:O
Katie:B-PER
Morley:I-PER
|:O
Telegraph:B-ORG
–:O
12:O
minutes:O
ago:O
Print:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-PER",
"I-PER",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O"
] | [
"Markets",
"close",
"in",
"1",
"hr",
"45",
"mins",
"Firms",
"cornered",
"by",
"watchdog",
"over",
"pension",
"freedom",
"blocks",
"By",
"Katie",
"Morley",
"|",
"Telegraph",
"–",
"12",
"minutes",
"ago",
"Print"
] |
finerord234 | 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: In
a
victory
for
Telegraph
Money
,
the
regulator
has
written
to
every
major
pension
provider
demanding
information
on
practices
which
are
preventing
savers
from
accessing
their
pensions
Answer: | In:O
a:O
victory:O
for:O
Telegraph:B-ORG
Money:I-ORG
,:O
the:O
regulator:O
has:O
written:O
to:O
every:O
major:O
pension:O
provider:O
demanding:O
information:O
on:O
practices:O
which:O
are:O
preventing:O
savers:O
from:O
accessing:O
their:O
pensions: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",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"In",
"a",
"victory",
"for",
"Telegraph",
"Money",
",",
"the",
"regulator",
"has",
"written",
"to",
"every",
"major",
"pension",
"provider",
"demanding",
"information",
"on",
"practices",
"which",
"are",
"preventing",
"savers",
"from",
"accessing",
"their",
"pensions"
] |
finerord235 | 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
Government
has
given
pension
providers
five
weeks
to
come
clean
about
how
they
are
blocking
over
55s
from
accessing
the
new
pension
freedoms
.
Answer: | The:O
Government:O
has:O
given:O
pension:O
providers:O
five:O
weeks:O
to:O
come:O
clean:O
about:O
how:O
they:O
are:O
blocking:O
over:O
55s:O
from:O
accessing:O
the:O
new:O
pension:O
freedoms:O
.:O | [
"O",
"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",
"Government",
"has",
"given",
"pension",
"providers",
"five",
"weeks",
"to",
"come",
"clean",
"about",
"how",
"they",
"are",
"blocking",
"over",
"55s",
"from",
"accessing",
"the",
"new",
"pension",
"freedoms",
"."
] |
finerord236 | 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: In
a
victory
for
Telegraph
Money
's
Make
Pension
Freedoms
Work
campaign
,
the
Financial
Conduct
Authority
has
written
to
every
major
pension
provider
demanding
information
on
practices
which
are
preventing
savers
from
accessing
their
pensions
.
Answer: | In:O
a:O
victory:O
for:O
Telegraph:B-ORG
Money:I-ORG
's:O
Make:O
Pension:O
Freedoms:O
Work:O
campaign:O
,:O
the:O
Financial:O
Conduct:O
Authority:O
has:O
written:O
to:O
every:O
major:O
pension:O
provider:O
demanding:O
information:O
on:O
practices:O
which:O
are:O
preventing:O
savers:O
from:O
accessing:O
their:O
pensions: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",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"In",
"a",
"victory",
"for",
"Telegraph",
"Money",
"'s",
"Make",
"Pension",
"Freedoms",
"Work",
"campaign",
",",
"the",
"Financial",
"Conduct",
"Authority",
"has",
"written",
"to",
"every",
"major",
"pension",
"provider",
"demanding",
"information",
"on",
"practices",
"which",
"are",
"preventing",
"savers",
"from",
"accessing",
"their",
"pensions",
"."
] |
finerord237 | 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
month
ministers
ordered
an
internal
inquiry
into
the
rip
-
offs
and
obstacles
that
have
"
handcuffed
"
savers
who
are
trying
to
use
their
pensions
more
flexibly
.
Answer: | Last:O
month:O
ministers:O
ordered:O
an:O
internal:O
inquiry:O
into:O
the:O
rip:O
-:O
offs:O
and:O
obstacles:O
that:O
have:O
":O
handcuffed:O
":O
savers:O
who:O
are:O
trying:O
to:O
use:O
their:O
pensions:O
more:O
flexibly:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Last",
"month",
"ministers",
"ordered",
"an",
"internal",
"inquiry",
"into",
"the",
"rip",
"-",
"offs",
"and",
"obstacles",
"that",
"have",
"\"",
"handcuffed",
"\"",
"savers",
"who",
"are",
"trying",
"to",
"use",
"their",
"pensions",
"more",
"flexibly",
"."
] |
finerord238 | 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: As
this
newspaper
has
repeatedly
highlighted
,
millions
of
people
are
in
one
way
or
another
being
blocked
from
accessing
their
money
.
Answer: | As:O
this:O
newspaper:O
has:O
repeatedly:O
highlighted:O
,:O
millions:O
of:O
people:O
are:O
in:O
one:O
way:O
or:O
another:O
being:O
blocked:O
from:O
accessing:O
their:O
money:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"As",
"this",
"newspaper",
"has",
"repeatedly",
"highlighted",
",",
"millions",
"of",
"people",
"are",
"in",
"one",
"way",
"or",
"another",
"being",
"blocked",
"from",
"accessing",
"their",
"money",
"."
] |
finerord239 | 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: We
started
our
campaign
with
the
aim
of
ensuring
these
savers
will
be
able
to
use
the
freedoms
without
complication
or
unfair
expense
.
Answer: | We:O
started:O
our:O
campaign:O
with:O
the:O
aim:O
of:O
ensuring:O
these:O
savers:O
will:O
be:O
able:O
to:O
use:O
the:O
freedoms:O
without:O
complication:O
or:O
unfair:O
expense:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"We",
"started",
"our",
"campaign",
"with",
"the",
"aim",
"of",
"ensuring",
"these",
"savers",
"will",
"be",
"able",
"to",
"use",
"the",
"freedoms",
"without",
"complication",
"or",
"unfair",
"expense",
"."
] |
finerord240 | 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
FCA
has
asked
firms
to
provide
information
on
five
key
areas
in
which
it
believes
there
are
potential
problems
.
Answer: | The:O
FCA:B-ORG
has:O
asked:O
firms:O
to:O
provide:O
information:O
on:O
five:O
key:O
areas:O
in:O
which:O
it:O
believes:O
there:O
are:O
potential:O
problems: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",
"FCA",
"has",
"asked",
"firms",
"to",
"provide",
"information",
"on",
"five",
"key",
"areas",
"in",
"which",
"it",
"believes",
"there",
"are",
"potential",
"problems",
"."
] |
finerord241 | 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: These
are
the
options
firms
offer
to
consumers
seeking
to
access
their
pension
savings
;
advice
requirements
for
consumers
transferring
out
of
pensions
;
how
firms
treat
insistent
clients
;
transfer
procedures
,
and
exit
charges
.
Answer: | These:O
are:O
the:O
options:O
firms:O
offer:O
to:O
consumers:O
seeking:O
to:O
access:O
their:O
pension:O
savings:O
;:O
advice:O
requirements:O
for:O
consumers:O
transferring:O
out:O
of:O
pensions:O
;:O
how:O
firms:O
treat:O
insistent:O
clients:O
;:O
transfer:O
procedures:O
,:O
and:O
exit:O
charges:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"These",
"are",
"the",
"options",
"firms",
"offer",
"to",
"consumers",
"seeking",
"to",
"access",
"their",
"pension",
"savings",
";",
"advice",
"requirements",
"for",
"consumers",
"transferring",
"out",
"of",
"pensions",
";",
"how",
"firms",
"treat",
"insistent",
"clients",
";",
"transfer",
"procedures",
",",
"and",
"exit",
"charges",
"."
] |
finerord242 | 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: •
Pension
freedoms
danger
:
the
essential
changes
you
need
to
make
long
before
you
're
55
•
Pension
freedoms
scandal
:
savers
blocked
from
using
new
rules
Answer: | •:O
Pension:O
freedoms:O
danger:O
::O
the:O
essential:O
changes:O
you:O
need:O
to:O
make:O
long:O
before:O
you:O
're:O
55:O
•:O
Pension:O
freedoms:O
scandal:O
::O
savers:O
blocked:O
from:O
using:O
new:O
rules:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"•",
"Pension",
"freedoms",
"danger",
":",
"the",
"essential",
"changes",
"you",
"need",
"to",
"make",
"long",
"before",
"you",
"'re",
"55",
"•",
"Pension",
"freedoms",
"scandal",
":",
"savers",
"blocked",
"from",
"using",
"new",
"rules"
] |
finerord243 | 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
FCA
said
:
"
We
recognise
that
the
timescale
for
the
delivery
of
this
data
is
short
,
but
given
the
interest
in
these
issues
we
expect
firms
to
comply
with
this
data
request
to
the
best
of
their
abilities
in
the
time
available
.
"
Answer: | The:O
FCA:B-ORG
said:O
::O
":O
We:O
recognise:O
that:O
the:O
timescale:O
for:O
the:O
delivery:O
of:O
this:O
data:O
is:O
short:O
,:O
but:O
given:O
the:O
interest:O
in:O
these:O
issues:O
we:O
expect:O
firms:O
to:O
comply:O
with:O
this:O
data:O
request:O
to:O
the:O
best:O
of:O
their:O
abilities:O
in:O
the:O
time:O
available: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",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"FCA",
"said",
":",
"\"",
"We",
"recognise",
"that",
"the",
"timescale",
"for",
"the",
"delivery",
"of",
"this",
"data",
"is",
"short",
",",
"but",
"given",
"the",
"interest",
"in",
"these",
"issues",
"we",
"expect",
"firms",
"to",
"comply",
"with",
"this",
"data",
"request",
"to",
"the",
"best",
"of",
"their",
"abilities",
"in",
"the",
"time",
"available",
".",
"\""
] |
finerord244 | 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
firms
fail
to
provide
the
required
information
they
could
be
fined
.
Answer: | If:O
firms:O
fail:O
to:O
provide:O
the:O
required:O
information:O
they:O
could:O
be:O
fined:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"If",
"firms",
"fail",
"to",
"provide",
"the",
"required",
"information",
"they",
"could",
"be",
"fined",
"."
] |
finerord245 | 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: •
katie.morley@telegraph.co.uk
Answer: | •:O
katie.morley@telegraph.co.uk:O | [
"O",
"O"
] | [
"•",
"katie.morley@telegraph.co.uk"
] |
finerord246 | 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: External
commercial
borrowings
(
ECB
)
by
companies
in
the
first
four
months
of
FY16
have
come
down
nearly
22
%
against
the
same
period
last
year
,
data
from
the
Reserve
Bank
of
India
(
RBI
)
show
.
Answer: | External:O
commercial:O
borrowings:O
(:O
ECB:O
):O
by:O
companies:O
in:O
the:O
first:O
four:O
months:O
of:O
FY16:O
have:O
come:O
down:O
nearly:O
22:O
%:O
against:O
the:O
same:O
period:O
last:O
year:O
,:O
data:O
from:O
the:O
Reserve:B-ORG
Bank:I-ORG
of:I-ORG
India:I-ORG
(:O
RBI:B-ORG
):O
show:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"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",
"I-ORG",
"I-ORG",
"I-ORG",
"O",
"B-ORG",
"O",
"O",
"O"
] | [
"External",
"commercial",
"borrowings",
"(",
"ECB",
")",
"by",
"companies",
"in",
"the",
"first",
"four",
"months",
"of",
"FY16",
"have",
"come",
"down",
"nearly",
"22",
"%",
"against",
"the",
"same",
"period",
"last",
"year",
",",
"data",
"from",
"the",
"Reserve",
"Bank",
"of",
"India",
"(",
"RBI",
")",
"show",
"."
] |
finerord247 | 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: Companies
’
ECB
between
April
and
July
stood
at
$
8.42
billion
compared
with
$
10.27
billion
in
the
corresponding
period
in
2014
,
reflecting
a
21.97
%
fall
.
Answer: | Companies:O
’:O
ECB:O
between:O
April:O
and:O
July:O
stood:O
at:O
$:O
8.42:O
billion:O
compared:O
with:O
$:O
10.27:O
billion:O
in:O
the:O
corresponding:O
period:O
in:O
2014:O
,:O
reflecting:O
a:O
21.97:O
%:O
fall:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Companies",
"’",
"ECB",
"between",
"April",
"and",
"July",
"stood",
"at",
"$",
"8.42",
"billion",
"compared",
"with",
"$",
"10.27",
"billion",
"in",
"the",
"corresponding",
"period",
"in",
"2014",
",",
"reflecting",
"a",
"21.97",
"%",
"fall",
"."
] |
finerord248 | 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: In
July
,
the
ECB
figure
stood
at
$
2.14
billion
which
is
way
below
the
$
3.7
billion
seen
in
July
2014
.
Answer: | In:O
July:O
,:O
the:O
ECB:O
figure:O
stood:O
at:O
$:O
2.14:O
billion:O
which:O
is:O
way:O
below:O
the:O
$:O
3.7:O
billion:O
seen:O
in:O
July:O
2014:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"In",
"July",
",",
"the",
"ECB",
"figure",
"stood",
"at",
"$",
"2.14",
"billion",
"which",
"is",
"way",
"below",
"the",
"$",
"3.7",
"billion",
"seen",
"in",
"July",
"2014",
"."
] |
finerord249 | 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: Manoj
Rane
,
the
MD
and
head
of
global
markets
and
treasury
at
BNP
Paribas
India
,
observes
that
the
drop
in
ECB
might
be
due
to
the
sluggishness
seen
in
the
investment
cycle
pick
-
up
.
Answer: | Manoj:B-PER
Rane:I-PER
,:O
the:O
MD:O
and:O
head:O
of:O
global:O
markets:O
and:O
treasury:O
at:O
BNP:B-ORG
Paribas:I-ORG
India:I-ORG
,:O
observes:O
that:O
the:O
drop:O
in:O
ECB:O
might:O
be:O
due:O
to:O
the:O
sluggishness:O
seen:O
in:O
the:O
investment:O
cycle:O
pick:O
-:O
up:O
.:O | [
"B-PER",
"I-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-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"
] | [
"Manoj",
"Rane",
",",
"the",
"MD",
"and",
"head",
"of",
"global",
"markets",
"and",
"treasury",
"at",
"BNP",
"Paribas",
"India",
",",
"observes",
"that",
"the",
"drop",
"in",
"ECB",
"might",
"be",
"due",
"to",
"the",
"sluggishness",
"seen",
"in",
"the",
"investment",
"cycle",
"pick",
"-",
"up",
"."
] |
finerord250 | 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: “
Significant
amount
of
ECBs
are
seen
when
the
capital
investment
cycle
picks
up
.
Answer: | “:O
Significant:O
amount:O
of:O
ECBs:O
are:O
seen:O
when:O
the:O
capital:O
investment:O
cycle:O
picks:O
up:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"“",
"Significant",
"amount",
"of",
"ECBs",
"are",
"seen",
"when",
"the",
"capital",
"investment",
"cycle",
"picks",
"up",
"."
] |
finerord251 | 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
is
evident
there
has
n’t
been
a
turnaround
in
the
capital
investment
cycle
.
Answer: | It:O
is:O
evident:O
there:O
has:O
n’t:O
been:O
a:O
turnaround:O
in:O
the:O
capital:O
investment:O
cycle:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"is",
"evident",
"there",
"has",
"n’t",
"been",
"a",
"turnaround",
"in",
"the",
"capital",
"investment",
"cycle",
"."
] |
finerord252 | 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: This
obviously
means
lesser
overall
borrowing
—
ECB
or
otherwise
,
”
he
said
.
Answer: | This:O
obviously:O
means:O
lesser:O
overall:O
borrowing:O
—:O
ECB:O
or:O
otherwise:O
,:O
”:O
he:O
said:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"This",
"obviously",
"means",
"lesser",
"overall",
"borrowing",
"—",
"ECB",
"or",
"otherwise",
",",
"”",
"he",
"said",
"."
] |
finerord253 | 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: Rane
also
points
out
that
ECBs
of
significant
amounts
can
only
be
done
by
corporates
that
have
a
good
rating
.
Answer: | Rane:B-PER
also:O
points:O
out:O
that:O
ECBs:O
of:O
significant:O
amounts:O
can:O
only:O
be:O
done:O
by:O
corporates:O
that:O
have:O
a:O
good:O
rating:O
.:O | [
"B-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Rane",
"also",
"points",
"out",
"that",
"ECBs",
"of",
"significant",
"amounts",
"can",
"only",
"be",
"done",
"by",
"corporates",
"that",
"have",
"a",
"good",
"rating",
"."
] |
finerord254 | 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: “
Considering
that
a
few
Indian
companies
have
a
global
rating
of
investment
grade
or
better
(
sovereign
itself
being
rated
lowest
investment
grade
BBB
-
)
,
it
may
be
possible
a
few
large
ticket
ECB
transactions
in
the
corresponding
period
last
year
may
have
inflated
the
total
number
,
”
he
said
.
Answer: | “:O
Considering:O
that:O
a:O
few:O
Indian:O
companies:O
have:O
a:O
global:O
rating:O
of:O
investment:O
grade:O
or:O
better:O
(:O
sovereign:O
itself:O
being:O
rated:O
lowest:O
investment:O
grade:O
BBB:O
-:O
):O
,:O
it:O
may:O
be:O
possible:O
a:O
few:O
large:O
ticket:O
ECB:O
transactions:O
in:O
the:O
corresponding:O
period:O
last:O
year:O
may:O
have:O
inflated:O
the:O
total:O
number: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",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"“",
"Considering",
"that",
"a",
"few",
"Indian",
"companies",
"have",
"a",
"global",
"rating",
"of",
"investment",
"grade",
"or",
"better",
"(",
"sovereign",
"itself",
"being",
"rated",
"lowest",
"investment",
"grade",
"BBB",
"-",
")",
",",
"it",
"may",
"be",
"possible",
"a",
"few",
"large",
"ticket",
"ECB",
"transactions",
"in",
"the",
"corresponding",
"period",
"last",
"year",
"may",
"have",
"inflated",
"the",
"total",
"number",
",",
"”",
"he",
"said",
"."
] |
finerord255 | 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: RBI
data
show
that
some
major
borrowers
in
July
were
Adani
Ports
and
Special
Economic
Zone
that
borrowed
$
650
million
in
two
tranches
,
Housing
Development
Finance
Corporation
borrowed
$
500
million
and
REC
borrowed
$
300
million
.
Answer: | RBI:B-ORG
data:O
show:O
that:O
some:O
major:O
borrowers:O
in:O
July:O
were:O
Adani:B-ORG
Ports:I-ORG
and:O
Special:B-ORG
Economic:I-ORG
Zone:I-ORG
that:O
borrowed:O
$:O
650:O
million:O
in:O
two:O
tranches:O
,:O
Housing:B-ORG
Development:I-ORG
Finance:I-ORG
Corporation:I-ORG
borrowed:O
$:O
500:O
million:O
and:O
REC:B-ORG
borrowed:O
$:O
300:O
million:O
.:O | [
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O",
"B-ORG",
"I-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"I-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O"
] | [
"RBI",
"data",
"show",
"that",
"some",
"major",
"borrowers",
"in",
"July",
"were",
"Adani",
"Ports",
"and",
"Special",
"Economic",
"Zone",
"that",
"borrowed",
"$",
"650",
"million",
"in",
"two",
"tranches",
",",
"Housing",
"Development",
"Finance",
"Corporation",
"borrowed",
"$",
"500",
"million",
"and",
"REC",
"borrowed",
"$",
"300",
"million",
"."
] |
finerord256 | 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: Moreover
,
a
significant
drop
in
the
domestic
corporate
bond
yields
might
have
also
led
to
a
shift
from
foreign
currency
borrowings
as
the
interest
rate
differential
has
narrowed
.
Answer: | Moreover:O
,:O
a:O
significant:O
drop:O
in:O
the:O
domestic:O
corporate:O
bond:O
yields:O
might:O
have:O
also:O
led:O
to:O
a:O
shift:O
from:O
foreign:O
currency:O
borrowings:O
as:O
the:O
interest:O
rate:O
differential:O
has:O
narrowed:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Moreover",
",",
"a",
"significant",
"drop",
"in",
"the",
"domestic",
"corporate",
"bond",
"yields",
"might",
"have",
"also",
"led",
"to",
"a",
"shift",
"from",
"foreign",
"currency",
"borrowings",
"as",
"the",
"interest",
"rate",
"differential",
"has",
"narrowed",
"."
] |
finerord257 | 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: 01
,
2015
12:19
am
Answer: | 01:O
,:O
2015:O
12:19:O
am:O | [
"O",
"O",
"O",
"O",
"O"
] | [
"01",
",",
"2015",
"12:19",
"am"
] |
finerord258 | 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: Tip
:
Use
comma
(
,
)
to
separate
multiple
quotes
.
Answer: | Tip:O
::O
Use:O
comma:O
(:O
,:O
):O
to:O
separate:O
multiple:O
quotes:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Tip",
":",
"Use",
"comma",
"(",
",",
")",
"to",
"separate",
"multiple",
"quotes",
"."
] |
finerord259 | 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: Learn
more
...
Answer: | Learn:O
more:O
...:O | [
"O",
"O",
"O"
] | [
"Learn",
"more",
"..."
] |
finerord260 | 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: Fri
,
Jul
10
,
2015
,
14:38
BST
-
UK
Markets
close
in
1
hr
52
mins
3
Stocks
To
Get
Your
Pulse
Racing
!
Answer: | Fri:O
,:O
Jul:O
10:O
,:O
2015:O
,:O
14:38:O
BST:O
-:O
UK:B-LOC
Markets:O
close:O
in:O
1:O
hr:O
52:O
mins:O
3:O
Stocks:O
To:O
Get:O
Your:O
Pulse:O
Racing: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"
] | [
"Fri",
",",
"Jul",
"10",
",",
"2015",
",",
"14:38",
"BST",
"-",
"UK",
"Markets",
"close",
"in",
"1",
"hr",
"52",
"mins",
"3",
"Stocks",
"To",
"Get",
"Your",
"Pulse",
"Racing",
"!"
] |
finerord261 | 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: Blinkx
Plc
,
Boohoo
.
Answer: | Blinkx:B-ORG
Plc:I-ORG
,:O
Boohoo:B-ORG
.:I-ORG | [
"B-ORG",
"I-ORG",
"O",
"B-ORG",
"I-ORG"
] | [
"Blinkx",
"Plc",
",",
"Boohoo",
"."
] |
finerord262 | 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: Com
PLC
And
Clinigen
Group
PLC
By
Peter
Stephens
|
Fool.co.uk
–
28
minutes
ago
647.00
+12.0000
Answer: | Com:I-ORG
PLC:I-ORG
And:O
Clinigen:B-ORG
Group:I-ORG
PLC:I-ORG
By:O
Peter:B-PER
Stephens:I-PER
|:O
Fool.co.uk:O
–:O
28:O
minutes:O
ago:O
647.00:O
+12.0000:O | [
"I-ORG",
"I-ORG",
"O",
"B-ORG",
"I-ORG",
"I-ORG",
"O",
"B-PER",
"I-PER",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Com",
"PLC",
"And",
"Clinigen",
"Group",
"PLC",
"By",
"Peter",
"Stephens",
"|",
"Fool.co.uk",
"–",
"28",
"minutes",
"ago",
"647.00",
"+12.0000"
] |
finerord263 | 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: One
of
the
great
things
about
investing
is
turning
your
hard
-
earned
cash
into
an
even
greater
amount
.
Answer: | One:O
of:O
the:O
great:O
things:O
about:O
investing:O
is:O
turning:O
your:O
hard:O
-:O
earned:O
cash:O
into:O
an:O
even:O
greater:O
amount:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"One",
"of",
"the",
"great",
"things",
"about",
"investing",
"is",
"turning",
"your",
"hard",
"-",
"earned",
"cash",
"into",
"an",
"even",
"greater",
"amount",
"."
] |
finerord264 | 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: Certainly
,
the
journey
between
those
two
places
is
not
always
a
smooth
one
and
,
in
the
intervening
period
,
the
value
of
your
investments
can
rise
and
fall
significantly
.
Answer: | Certainly:O
,:O
the:O
journey:O
between:O
those:O
two:O
places:O
is:O
not:O
always:O
a:O
smooth:O
one:O
and:O
,:O
in:O
the:O
intervening:O
period:O
,:O
the:O
value:O
of:O
your:O
investments:O
can:O
rise:O
and:O
fall:O
significantly:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Certainly",
",",
"the",
"journey",
"between",
"those",
"two",
"places",
"is",
"not",
"always",
"a",
"smooth",
"one",
"and",
",",
"in",
"the",
"intervening",
"period",
",",
"the",
"value",
"of",
"your",
"investments",
"can",
"rise",
"and",
"fall",
"significantly",
"."
] |
finerord265 | 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
,
for
long
term
investors
,
what
matters
is
that
the
total
return
is
relatively
high
.
Answer: | However:O
,:O
for:O
long:O
term:O
investors:O
,:O
what:O
matters:O
is:O
that:O
the:O
total:O
return:O
is:O
relatively:O
high:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
",",
"for",
"long",
"term",
"investors",
",",
"what",
"matters",
"is",
"that",
"the",
"total",
"return",
"is",
"relatively",
"high",
"."
] |
finerord266 | 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
,
such
a
prospect
is
likely
to
get
any
investor
's
pulse
racing
,
with
stocks
that
offer
the
potential
for
high
levels
of
growth
and
capital
gains
being
among
the
most
sought
after
.
Answer: | Clearly:O
,:O
such:O
a:O
prospect:O
is:O
likely:O
to:O
get:O
any:O
investor:O
's:O
pulse:O
racing:O
,:O
with:O
stocks:O
that:O
offer:O
the:O
potential:O
for:O
high:O
levels:O
of:O
growth:O
and:O
capital:O
gains:O
being:O
among:O
the:O
most:O
sought:O
after:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Clearly",
",",
"such",
"a",
"prospect",
"is",
"likely",
"to",
"get",
"any",
"investor",
"'s",
"pulse",
"racing",
",",
"with",
"stocks",
"that",
"offer",
"the",
"potential",
"for",
"high",
"levels",
"of",
"growth",
"and",
"capital",
"gains",
"being",
"among",
"the",
"most",
"sought",
"after",
"."
] |
finerord267 | 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
,
on
that
front
,
there
are
a
number
of
great
options
for
investors
to
choose
from
at
the
present
time
.
Answer: | And:O
,:O
on:O
that:O
front:O
,:O
there:O
are:O
a:O
number:O
of:O
great:O
options:O
for:O
investors:O
to:O
choose:O
from:O
at:O
the:O
present:O
time:O
.: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",
",",
"on",
"that",
"front",
",",
"there",
"are",
"a",
"number",
"of",
"great",
"options",
"for",
"investors",
"to",
"choose",
"from",
"at",
"the",
"present",
"time",
"."
] |
finerord268 | 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: For
example
,
online
fashion
retailer
,
Boohoo
.
Answer: | For:O
example:O
,:O
online:O
fashion:O
retailer:O
,:O
Boohoo:B-ORG
.:I-ORG | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG"
] | [
"For",
"example",
",",
"online",
"fashion",
"retailer",
",",
"Boohoo",
"."
] |
finerord269 | 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: Com
(
LSE
:
BOO
)
,
is
set
to
benefit
from
an
improving
UK
and
global
economy
as
it
seeks
to
develop
customer
loyalty
.
Answer: | Com:I-ORG
(:O
LSE:B-ORG
::O
BOO:B-ORG
):O
,:O
is:O
set:O
to:O
benefit:O
from:O
an:O
improving:O
UK:B-LOC
and:O
global:O
economy:O
as:O
it:O
seeks:O
to:O
develop:O
customer:O
loyalty:O
.:O | [
"I-ORG",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-LOC",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Com",
"(",
"LSE",
":",
"BOO",
")",
",",
"is",
"set",
"to",
"benefit",
"from",
"an",
"improving",
"UK",
"and",
"global",
"economy",
"as",
"it",
"seeks",
"to",
"develop",
"customer",
"loyalty",
"."
] |
finerord270 | 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: Of
course
,
this
takes
time
to
acquire
and
,
with
there
being
such
vast
competition
among
retailers
that
are
focused
on
the
lucrative
teen
and
twentysomething
marketplace
,
Boohoo
.
Answer: | Of:O
course:O
,:O
this:O
takes:O
time:O
to:O
acquire:O
and:O
,:O
with:O
there:O
being:O
such:O
vast:O
competition:O
among:O
retailers:O
that:O
are:O
focused:O
on:O
the:O
lucrative:O
teen:O
and:O
twentysomething:O
marketplace:O
,:O
Boohoo: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",
"B-ORG",
"I-ORG"
] | [
"Of",
"course",
",",
"this",
"takes",
"time",
"to",
"acquire",
"and",
",",
"with",
"there",
"being",
"such",
"vast",
"competition",
"among",
"retailers",
"that",
"are",
"focused",
"on",
"the",
"lucrative",
"teen",
"and",
"twentysomething",
"marketplace",
",",
"Boohoo",
"."
] |
finerord271 | 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: Com
is
set
to
be
a
relatively
volatile
stock
to
own
.
Answer: | Com:I-ORG
is:O
set:O
to:O
be:O
a:O
relatively:O
volatile:O
stock:O
to:O
own:O
.:O | [
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Com",
"is",
"set",
"to",
"be",
"a",
"relatively",
"volatile",
"stock",
"to",
"own",
"."
] |
finerord272 | 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
,
looking
ahead
to
its
earnings
growth
potential
,
it
could
prove
to
be
a
hugely
exciting
investment
.
Answer: | However:O
,:O
looking:O
ahead:O
to:O
its:O
earnings:O
growth:O
potential:O
,:O
it:O
could:O
prove:O
to:O
be:O
a:O
hugely:O
exciting:O
investment:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
",",
"looking",
"ahead",
"to",
"its",
"earnings",
"growth",
"potential",
",",
"it",
"could",
"prove",
"to",
"be",
"a",
"hugely",
"exciting",
"investment",
"."
] |
finerord273 | 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
because
it
is
forecast
to
increase
its
bottom
line
by
43
%
in
the
current
year
,
followed
by
growth
of
25
%
next
year
.
Answer: | That:O
's:O
because:O
it:O
is:O
forecast:O
to:O
increase:O
its:O
bottom:O
line:O
by:O
43:O
%:O
in:O
the:O
current:O
year:O
,:O
followed:O
by:O
growth:O
of:O
25:O
%:O
next:O
year:O
.:O | [
"O",
"O",
"O",
"O",
"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",
"'s",
"because",
"it",
"is",
"forecast",
"to",
"increase",
"its",
"bottom",
"line",
"by",
"43",
"%",
"in",
"the",
"current",
"year",
",",
"followed",
"by",
"growth",
"of",
"25",
"%",
"next",
"year",
"."
] |
finerord274 | 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
met
,
that
would
be
a
stunning
rate
of
growth
and
would
easily
surpass
the
vast
majority
of
Boohoo
.
Answer: | If:O
met:O
,:O
that:O
would:O
be:O
a:O
stunning:O
rate:O
of:O
growth:O
and:O
would:O
easily:O
surpass:O
the:O
vast:O
majority:O
of:O
Boohoo:B-ORG
.:I-ORG | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG"
] | [
"If",
"met",
",",
"that",
"would",
"be",
"a",
"stunning",
"rate",
"of",
"growth",
"and",
"would",
"easily",
"surpass",
"the",
"vast",
"majority",
"of",
"Boohoo",
"."
] |
finerord275 | 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: Com
's
listed
peers
.
Answer: | Com:I-ORG
's:O
listed:O
peers:O
.:O | [
"I-ORG",
"O",
"O",
"O",
"O"
] | [
"Com",
"'s",
"listed",
"peers",
"."
] |
finerord276 | 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: In
fact
,
it
would
mean
that
the
company
's
bottom
line
would
rise
by
79
%
over
the
next
two
years
and
,
despite
this
,
it
trades
on
a
price
to
earnings
growth
(
PEG
)
ratio
of
just
0.8
.
Answer: | In:O
fact:O
,:O
it:O
would:O
mean:O
that:O
the:O
company:O
's:O
bottom:O
line:O
would:O
rise:O
by:O
79:O
%:O
over:O
the:O
next:O
two:O
years:O
and:O
,:O
despite:O
this:O
,:O
it:O
trades:O
on:O
a:O
price:O
to:O
earnings:O
growth:O
(:O
PEG:O
):O
ratio:O
of:O
just:O
0.8:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"In",
"fact",
",",
"it",
"would",
"mean",
"that",
"the",
"company",
"'s",
"bottom",
"line",
"would",
"rise",
"by",
"79",
"%",
"over",
"the",
"next",
"two",
"years",
"and",
",",
"despite",
"this",
",",
"it",
"trades",
"on",
"a",
"price",
"to",
"earnings",
"growth",
"(",
"PEG",
")",
"ratio",
"of",
"just",
"0.8",
"."
] |
finerord277 | 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: This
indicates
that
it
has
a
sufficiently
wide
margin
of
safety
to
post
significant
share
price
gains
moving
forward
.
Answer: | This:O
indicates:O
that:O
it:O
has:O
a:O
sufficiently:O
wide:O
margin:O
of:O
safety:O
to:O
post:O
significant:O
share:O
price:O
gains:O
moving:O
forward:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"This",
"indicates",
"that",
"it",
"has",
"a",
"sufficiently",
"wide",
"margin",
"of",
"safety",
"to",
"post",
"significant",
"share",
"price",
"gains",
"moving",
"forward",
"."
] |
finerord278 | 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: Likewise
,
pharmaceutical
company
,
Clinigen
(
LSE
:
CLIN
)
,
also
has
an
exciting
medium
term
outlook
.
Answer: | Likewise:O
,:O
pharmaceutical:O
company:O
,:O
Clinigen:B-ORG
(:O
LSE:B-ORG
::O
CLIN:B-ORG
):O
,:O
also:O
has:O
an:O
exciting:O
medium:O
term:O
outlook:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Likewise",
",",
"pharmaceutical",
"company",
",",
"Clinigen",
"(",
"LSE",
":",
"CLIN",
")",
",",
"also",
"has",
"an",
"exciting",
"medium",
"term",
"outlook",
"."
] |
finerord279 | 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: Although
its
earnings
are
set
to
rise
by
just
1
%
this
year
,
its
bottom
line
is
expected
to
soar
by
as
much
as
29
%
next
year
,
which
could
act
as
a
positive
catalyst
for
its
share
price
.
Answer: | Although:O
its:O
earnings:O
are:O
set:O
to:O
rise:O
by:O
just:O
1:O
%:O
this:O
year:O
,:O
its:O
bottom:O
line:O
is:O
expected:O
to:O
soar:O
by:O
as:O
much:O
as:O
29:O
%:O
next:O
year:O
,:O
which:O
could:O
act:O
as:O
a:O
positive:O
catalyst:O
for:O
its:O
share:O
price:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Although",
"its",
"earnings",
"are",
"set",
"to",
"rise",
"by",
"just",
"1",
"%",
"this",
"year",
",",
"its",
"bottom",
"line",
"is",
"expected",
"to",
"soar",
"by",
"as",
"much",
"as",
"29",
"%",
"next",
"year",
",",
"which",
"could",
"act",
"as",
"a",
"positive",
"catalyst",
"for",
"its",
"share",
"price",
"."
] |
finerord280 | 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: Certainly
,
much
of
this
growth
has
already
been
priced
in
,
with
Clinigen
's
share
price
having
risen
by
23
%
since
the
turn
of
the
year
.
Answer: | Certainly:O
,:O
much:O
of:O
this:O
growth:O
has:O
already:O
been:O
priced:O
in:O
,:O
with:O
Clinigen:B-ORG
's:O
share:O
price:O
having:O
risen:O
by:O
23:O
%:O
since:O
the:O
turn:O
of:O
the:O
year: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"
] | [
"Certainly",
",",
"much",
"of",
"this",
"growth",
"has",
"already",
"been",
"priced",
"in",
",",
"with",
"Clinigen",
"'s",
"share",
"price",
"having",
"risen",
"by",
"23",
"%",
"since",
"the",
"turn",
"of",
"the",
"year",
"."
] |
finerord281 | 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
,
with
its
shares
having
a
price
to
earnings
(
P/E
)
ratio
of
26.1
,
its
PEG
ratio
of
0.7
offers
significant
upside
.
Answer: | However:O
,:O
with:O
its:O
shares:O
having:O
a:O
price:O
to:O
earnings:O
(:O
P/E:O
):O
ratio:O
of:O
26.1:O
,:O
its:O
PEG:O
ratio:O
of:O
0.7:O
offers:O
significant:O
upside:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
",",
"with",
"its",
"shares",
"having",
"a",
"price",
"to",
"earnings",
"(",
"P/E",
")",
"ratio",
"of",
"26.1",
",",
"its",
"PEG",
"ratio",
"of",
"0.7",
"offers",
"significant",
"upside",
"."
] |
finerord282 | 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: Of
course
,
there
are
a
number
of
turnaround
stocks
that
also
offer
future
growth
prospects
and
excitement
for
their
investors
.
Answer: | Of:O
course:O
,:O
there:O
are:O
a:O
number:O
of:O
turnaround:O
stocks:O
that:O
also:O
offer:O
future:O
growth:O
prospects:O
and:O
excitement:O
for:O
their:O
investors:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Of",
"course",
",",
"there",
"are",
"a",
"number",
"of",
"turnaround",
"stocks",
"that",
"also",
"offer",
"future",
"growth",
"prospects",
"and",
"excitement",
"for",
"their",
"investors",
"."
] |
finerord283 | 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: One
such
stock
is
online
advertising
specialist
,
Blinkx
(
LSE
:
BLNX
)
.
Answer: | One:O
such:O
stock:O
is:O
online:O
advertising:O
specialist:O
,:O
Blinkx:B-ORG
(:O
LSE:B-ORG
::O
BLNX:B-ORG
):O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"B-ORG",
"O",
"O"
] | [
"One",
"such",
"stock",
"is",
"online",
"advertising",
"specialist",
",",
"Blinkx",
"(",
"LSE",
":",
"BLNX",
")",
"."
] |
finerord284 | 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
is
in
the
midst
of
a
major
restructuring
,
rebranding
and
acquisition
spree
as
its
management
team
goes
all
out
to
try
and
reverse
the
disappointing
performance
that
has
turned
a
healthy
and
rising
black
bottom
line
into
a
red
one
.
Answer: | It:O
is:O
in:O
the:O
midst:O
of:O
a:O
major:O
restructuring:O
,:O
rebranding:O
and:O
acquisition:O
spree:O
as:O
its:O
management:O
team:O
goes:O
all:O
out:O
to:O
try:O
and:O
reverse:O
the:O
disappointing:O
performance:O
that:O
has:O
turned:O
a:O
healthy:O
and:O
rising:O
black:O
bottom:O
line:O
into:O
a:O
red:O
one:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"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",
"is",
"in",
"the",
"midst",
"of",
"a",
"major",
"restructuring",
",",
"rebranding",
"and",
"acquisition",
"spree",
"as",
"its",
"management",
"team",
"goes",
"all",
"out",
"to",
"try",
"and",
"reverse",
"the",
"disappointing",
"performance",
"that",
"has",
"turned",
"a",
"healthy",
"and",
"rising",
"black",
"bottom",
"line",
"into",
"a",
"red",
"one",
"."
] |
finerord285 | 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: Looking
ahead
,
Blinkx
is
set
to
post
a
pretax
loss
in
the
current
year
as
well
as
next
year
.
Answer: | Looking:O
ahead:O
,:O
Blinkx:B-ORG
is:O
set:O
to:O
post:O
a:O
pretax:O
loss:O
in:O
the:O
current:O
year:O
as:O
well:O
as:O
next:O
year:O
.:O | [
"O",
"O",
"O",
"B-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Looking",
"ahead",
",",
"Blinkx",
"is",
"set",
"to",
"post",
"a",
"pretax",
"loss",
"in",
"the",
"current",
"year",
"as",
"well",
"as",
"next",
"year",
"."
] |
finerord286 | 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
scale
of
the
loss
is
due
to
fall
from
£
16.5
m
last
year
to
just
£
0.65
m
next
year
.
Answer: | However:O
,:O
the:O
scale:O
of:O
the:O
loss:O
is:O
due:O
to:O
fall:O
from:O
£:O
16.5:O
m:O
last:O
year:O
to:O
just:O
£:O
0.65:O
m:O
next:O
year:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"However",
",",
"the",
"scale",
"of",
"the",
"loss",
"is",
"due",
"to",
"fall",
"from",
"£",
"16.5",
"m",
"last",
"year",
"to",
"just",
"£",
"0.65",
"m",
"next",
"year",
"."
] |
finerord287 | 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
a
sound
strategy
and
improving
outlook
,
investor
sentiment
could
pick
up
and
push
Blinkx
's
share
price
significantly
higher
.
Answer: | And:O
,:O
with:O
a:O
sound:O
strategy:O
and:O
improving:O
outlook:O
,:O
investor:O
sentiment:O
could:O
pick:O
up:O
and:O
push:O
Blinkx:B-ORG
's:O
share:O
price:O
significantly:O
higher: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"
] | [
"And",
",",
"with",
"a",
"sound",
"strategy",
"and",
"improving",
"outlook",
",",
"investor",
"sentiment",
"could",
"pick",
"up",
"and",
"push",
"Blinkx",
"'s",
"share",
"price",
"significantly",
"higher",
"."
] |
finerord288 | 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: Of
course
,
there
are
a
number
of
other
exciting
stocks
that
could
be
worth
buying
right
now
and
,
with
that
in
mind
,
the
analysts
at
The
Motley
Fool
have
written
a
free
and
without
obligation
guide
called
1
Top
Small
-
Cap
Stock
From
The
Motley
Fool
.
Answer: | Of:O
course:O
,:O
there:O
are:O
a:O
number:O
of:O
other:O
exciting:O
stocks:O
that:O
could:O
be:O
worth:O
buying:O
right:O
now:O
and:O
,:O
with:O
that:O
in:O
mind:O
,:O
the:O
analysts:O
at:O
The:O
Motley:B-ORG
Fool:I-ORG
have:O
written:O
a:O
free:O
and:O
without:O
obligation:O
guide:O
called:O
1:O
Top:O
Small:O
-:O
Cap:O
Stock:O
From:O
The:O
Motley:B-ORG
Fool: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",
"B-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"B-ORG",
"I-ORG",
"O"
] | [
"Of",
"course",
",",
"there",
"are",
"a",
"number",
"of",
"other",
"exciting",
"stocks",
"that",
"could",
"be",
"worth",
"buying",
"right",
"now",
"and",
",",
"with",
"that",
"in",
"mind",
",",
"the",
"analysts",
"at",
"The",
"Motley",
"Fool",
"have",
"written",
"a",
"free",
"and",
"without",
"obligation",
"guide",
"called",
"1",
"Top",
"Small",
"-",
"Cap",
"Stock",
"From",
"The",
"Motley",
"Fool",
"."
] |
finerord289 | 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
company
in
question
may
have
flown
under
your
investment
radar
until
now
,
but
could
help
you
to
build
a
great
income
from
your
investments
and
retire
early
,
pay
off
the
mortgage
,
or
simply
enjoy
a
more
abundant
lifestyle
.
Answer: | The:O
company:O
in:O
question:O
may:O
have:O
flown:O
under:O
your:O
investment:O
radar:O
until:O
now:O
,:O
but:O
could:O
help:O
you:O
to:O
build:O
a:O
great:O
income:O
from:O
your:O
investments:O
and:O
retire:O
early:O
,:O
pay:O
off:O
the:O
mortgage:O
,:O
or:O
simply:O
enjoy:O
a:O
more:O
abundant:O
lifestyle:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"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",
"company",
"in",
"question",
"may",
"have",
"flown",
"under",
"your",
"investment",
"radar",
"until",
"now",
",",
"but",
"could",
"help",
"you",
"to",
"build",
"a",
"great",
"income",
"from",
"your",
"investments",
"and",
"retire",
"early",
",",
"pay",
"off",
"the",
"mortgage",
",",
"or",
"simply",
"enjoy",
"a",
"more",
"abundant",
"lifestyle",
"."
] |
finerord290 | 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: Click
here
to
find
out
all
about
it
-
it
's
completely
free
and
comes
without
any
obligation
.
Answer: | Click:O
here:O
to:O
find:O
out:O
all:O
about:O
it:O
-:O
it:O
's:O
completely:O
free:O
and:O
comes:O
without:O
any:O
obligation:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Click",
"here",
"to",
"find",
"out",
"all",
"about",
"it",
"-",
"it",
"'s",
"completely",
"free",
"and",
"comes",
"without",
"any",
"obligation",
"."
] |
finerord291 | 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: Peter
Stephens
owns
shares
of
Clinigen
.
Answer: | Peter:B-PER
Stephens:I-PER
owns:O
shares:O
of:O
Clinigen:B-ORG
.:O | [
"B-PER",
"I-PER",
"O",
"O",
"O",
"B-ORG",
"O"
] | [
"Peter",
"Stephens",
"owns",
"shares",
"of",
"Clinigen",
"."
] |
finerord292 | 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
Motley
Fool
UK
has
recommended
Clinigen
.
Answer: | The:O
Motley:B-ORG
Fool:I-ORG
UK:I-ORG
has:O
recommended:O
Clinigen:B-ORG
.:O | [
"O",
"B-ORG",
"I-ORG",
"I-ORG",
"O",
"O",
"B-ORG",
"O"
] | [
"The",
"Motley",
"Fool",
"UK",
"has",
"recommended",
"Clinigen",
"."
] |
finerord293 | 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: We
Fools
do
n't
all
hold
the
same
opinions
,
but
we
all
believe
that
considering
a
diverse
range
of
insights
makes
us
better
investors
.
Answer: | We:O
Fools:B-ORG
do:O
n't:O
all:O
hold:O
the:O
same:O
opinions:O
,:O
but:O
we:O
all:O
believe:O
that:O
considering:O
a:O
diverse:O
range:O
of:O
insights:O
makes:O
us:O
better:O
investors: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",
"O"
] | [
"We",
"Fools",
"do",
"n't",
"all",
"hold",
"the",
"same",
"opinions",
",",
"but",
"we",
"all",
"believe",
"that",
"considering",
"a",
"diverse",
"range",
"of",
"insights",
"makes",
"us",
"better",
"investors",
"."
] |
finerord294 | 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: View
Photo
Answer: | View:O
Photo:O | [
"O",
"O"
] | [
"View",
"Photo"
] |
finerord295 | 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
Athens
Stock
Exchange
has
plunged
22.86
%
this
morning
as
markets
reopen
for
the
first
time
in
five
weeks
.
Answer: | The:O
Athens:B-ORG
Stock:I-ORG
Exchange:I-ORG
has:O
plunged:O
22.86:O
%:O
this:O
morning:O
as:O
markets:O
reopen:O
for:O
the:O
first:O
time:O
in:O
five:O
weeks:O
.:O | [
"O",
"B-ORG",
"I-ORG",
"I-ORG",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"The",
"Athens",
"Stock",
"Exchange",
"has",
"plunged",
"22.86",
"%",
"this",
"morning",
"as",
"markets",
"reopen",
"for",
"the",
"first",
"time",
"in",
"five",
"weeks",
"."
] |
finerord296 | 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
has
been
closed
whilst
capital
controls
have
been
in
place
.
Answer: | It:O
has:O
been:O
closed:O
whilst:O
capital:O
controls:O
have:O
been:O
in:O
place:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"It",
"has",
"been",
"closed",
"whilst",
"capital",
"controls",
"have",
"been",
"in",
"place",
"."
] |
finerord297 | 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
Athex
Large
Cap
index
which
measure
the
performance
of
Greece
's
largest
listed
companies
closed
at
241.22
points
on
Friday
June
26
.
Answer: | The:O
Athex:O
Large:O
Cap:O
index:O
which:O
measure:O
the:O
performance:O
of:O
Greece:O
's:O
largest:O
listed:O
companies:O
closed:O
at:O
241.22:O
points:O
on:O
Friday:O
June:O
26:O
.:O | [
"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",
"Athex",
"Large",
"Cap",
"index",
"which",
"measure",
"the",
"performance",
"of",
"Greece",
"'s",
"largest",
"listed",
"companies",
"closed",
"at",
"241.22",
"points",
"on",
"Friday",
"June",
"26",
"."
] |
finerord298 | 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: Since
then
in
has
remained
closed
.
Answer: | Since:O
then:O
in:O
has:O
remained:O
closed:O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"Since",
"then",
"in",
"has",
"remained",
"closed",
"."
] |
finerord299 | 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: This
makes
the
combined
value
of
the
index
£
13.4bn
(
€19bn
)
.
Answer: | This:O
makes:O
the:O
combined:O
value:O
of:O
the:O
index:O
£:O
13.4bn:O
(:O
€19bn:O
):O
.:O | [
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O",
"O"
] | [
"This",
"makes",
"the",
"combined",
"value",
"of",
"the",
"index",
"£",
"13.4bn",
"(",
"€19bn",
")",
"."
] |