Spaces:
Running
Running
GitHub Actions commited on
Commit ·
b44e8fd
1
Parent(s): e469aff
Sync from GitHub · 2026-10-20 08:50 UTC
Browse files- news/classify.py +16 -0
news/classify.py
CHANGED
|
@@ -28,11 +28,27 @@ Read the title and text given, then output ONLY a JSON object with these exact f
|
|
| 28 |
Business type taxonomy (use these ids exactly, do not invent new ones):
|
| 29 |
{labels_for_prompt()}
|
| 30 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 31 |
Examples:
|
| 32 |
- A new CBN forex directive raising import costs -> impact=threat, category=policy, business_types=[relevant import/trade subsectors], location=Nationwide
|
| 33 |
- A flood warning for Lagos -> impact=threat, category=weather, business_types=[subsectors with physical premises/stock in the area], location=Lagos
|
| 34 |
- A state SME grant with an application deadline of 2026-12-01 -> impact=opportunity, category=funding, deadline=2026-12-01
|
| 35 |
- A tax holiday for new small businesses with no stated end date -> impact=opportunity, category=policy, deadline=null
|
|
|
|
|
|
|
|
|
|
|
|
|
| 36 |
|
| 37 |
If the item is not genuinely business-relevant, or you cannot determine a category, business
|
| 38 |
type, or location with reasonable confidence, leave the relevant field null/empty rather than
|
|
|
|
| 28 |
Business type taxonomy (use these ids exactly, do not invent new ones):
|
| 29 |
{labels_for_prompt()}
|
| 30 |
|
| 31 |
+
"threat" and "opportunity" are reserved for items with a CONCRETE, near-term consequence for how
|
| 32 |
+
a small business actually operates — a cost that goes up, a new restriction or compliance
|
| 33 |
+
requirement, a market or supply disruption, a scheme/grant/program it could apply to, a new
|
| 34 |
+
customer segment or channel opening up. If the only effect is on government finances, a
|
| 35 |
+
company's share price, politics, or the general public, and there's no specific operational
|
| 36 |
+
change a small-business owner would need to act on, that is "neutral" even if the headline sounds
|
| 37 |
+
dramatic. A single incident (an accident, a crime, an arrest) is "neutral" unless the text itself
|
| 38 |
+
states a resulting regulatory or operational change businesses must respond to. An aspirational
|
| 39 |
+
government target or long-term roadmap with no specific program, deadline, or eligibility a
|
| 40 |
+
business could act on today is "neutral", not "opportunity" — reserve "opportunity" for something
|
| 41 |
+
a business owner could actually apply to, access, or benefit from now.
|
| 42 |
+
|
| 43 |
Examples:
|
| 44 |
- A new CBN forex directive raising import costs -> impact=threat, category=policy, business_types=[relevant import/trade subsectors], location=Nationwide
|
| 45 |
- A flood warning for Lagos -> impact=threat, category=weather, business_types=[subsectors with physical premises/stock in the area], location=Lagos
|
| 46 |
- A state SME grant with an application deadline of 2026-12-01 -> impact=opportunity, category=funding, deadline=2026-12-01
|
| 47 |
- A tax holiday for new small businesses with no stated end date -> impact=opportunity, category=policy, deadline=null
|
| 48 |
+
- A plane makes an emergency landing with no stated regulatory fallout -> impact=neutral, category=other (an isolated incident, not a business-operational change)
|
| 49 |
+
- A senator publicly criticising a regulator's pace, with no rule actually changed yet -> impact=neutral, category=policy (nothing has changed for a business yet)
|
| 50 |
+
- A 10-year national capital-market target or roadmap with no program a business can apply to today -> impact=neutral, category=policy (aspirational, not actionable)
|
| 51 |
+
- A stock exchange index falling on a single trading day -> impact=neutral, category=other unless the text names a specific operational consequence for non-listed small businesses
|
| 52 |
|
| 53 |
If the item is not genuinely business-relevant, or you cannot determine a category, business
|
| 54 |
type, or location with reasonable confidence, leave the relevant field null/empty rather than
|