Representing CrunchBase IPOs in FIBO

CrunchBase has a table ipos with the following fields (see ipos-sample.csv):

field	type	descr
uuid	string	Unique identifier
name	string	Entity name
permalink	string	Suffix of url. Sometimes changes
url	anyURI	Full Crunchbase URL
rank	integer	Crunchbase rank (smaller is 'more important'). Optional since many Crunchbase entities don't have a rank (but the main ones do)
created at	dateTime	When the Crunchbase record was created
updated at	dateTime	When the Crunchbase record was updated
organization	Agent	Which company was listed
exchange symbol	string	Exchange code. Uses internal Crunchbase codes that are ambiguous, should better use MIC
stock symbol	string	Ticker on the exchange
went public on	dateTime	When the company went public (IPO date)
share price in US dollars	decimal	The share price for the stock at the time of IPO, in US dollars
share price in local currency	decimal	The share price for the stock at the time of IPO, in local currency
share price currency code	string	Local currency of share price
valuation price in US dollars	decimal	Valuation of the Organization at IPO, in US dollars
valuation price in local currency	decimal	Valuation of the Organization at IPO, in local currency
valuation price currency code	string	Local currency of the valuation
money raised in US dollars	decimal	Total amount raised from the IPO, in US dollars
money raised in local currency	decimal	Total amount raised from the IPO, in local currency
money raised currency code	string	Local currency of the total amount raised

• The first 7 fields are present in pretty much any CB entity
• The next 13 fields are specific to this entity (IPO)

In a simple semantic representation, I've represented this as one node (see CrunchBase Challenge that shows the complete CB model of 18 entities).

Now I represented IPOs in FIBO by using the 2022Q2 release (see Converting FIBO from RDF to Turtle).

The result is a complex graph:

This is generated from ipos.ttl using rdfpuml and the latest version of PlantUML 1.2022.6

• This model has 25 nodes (of which 11 are shared with other IPOs, eg the currencies and currency codes)
• It uses terms from 16 FIBO ontologies (see prefixes.ttl).

Why The Complexity?

• FIBO distinguishes Issuer (role) from the agent playing that role
• FIBO distinguishes Offering (the IPO), Share, Listing (of the share at an exchange), Ticker (a ReassignableIdentifier)
• FIBO represents the financials as explicit nodes (and MarketCap as 2 nodes). There are 6: total Price (money raised), MarketCap (valuation), Price per share; in national currency and USD
• FIBO represents the stock exchange and its code as two separate nodes
• Finally, FIBO represents currencies and their codes as two nodes each. There are 4 currencies involved.

Possible Improvements

• DONE: Asked the FIBO people to validate this representation and reflected changes suggested by Elisa Kendall and Pawel Garbacz (Mereolog).
• DONE: Added rdfs:label to each node
• DONE: Changed monetary node patterns in "national currency" vs in USD to be like this:

<cb/ipo/(uuid)/pricePerShare/(share_price_currency_code)>      vs <cb/ipo/(uuid)/pricePerShare/USD>
<cb/ipo/(uuid)/marketCap/(valuation_price_currency_code)>      vs <cb/ipo/(uuid)/marketCap/USD>
<cb/ipo/(uuid)/marketCapValue/(valuation_price_currency_code)> vs <cb/ipo/(uuid)/marketCapValue/USD>

• Previously they were like this:

<cb/ipo/(uuid)/pricePerShare>                                  vs <cb/ipo/(uuid)/pricePerShareUsd>
<cb/ipo/(uuid)/marketCap>                                      vs <cb/ipo/(uuid)/marketCapUsd>
<cb/ipo/(uuid)/marketCapValue>                                 vs <cb/ipo/(uuid)/marketCapValueUsd>

• But many IPOs are in the US, so we can save on nodes if we use URLs that incorporate the currency code. The difference is subtle but crucial: it effectively merges the monetary nodes of US IPOs.