Triple
T4382390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bloomberg L.P. |
E99160
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial information services company |
C13324
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: financial information services company Context triple: [Bloomberg L.P., instanceOf, financial information services company]
-
A.
financial market infrastructure company
A financial market infrastructure company provides the core systems, platforms, and services that enable the trading, clearing, settlement, and reporting of financial instruments in a safe, efficient, and regulated manner.
-
B.
information services provider
chosen
An information services provider is an entity that collects, processes, and delivers data, analysis, or knowledge-based content to users or organizations through various digital or physical channels.
-
C.
financial news company
A financial news company is an organization that gathers, analyzes, and disseminates timely information and insights about markets, economies, and businesses to investors, professionals, and the public.
-
D.
financial institution
A financial institution is an organization that manages money and financial services, such as accepting deposits, providing loans, facilitating investments, and enabling payment transactions for individuals, businesses, and governments.
-
E.
financial data platform
A financial data platform is a centralized system that aggregates, normalizes, analyzes, and distributes financial information and market data to users and applications in real time.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
Created at: March 12, 2026, 11:18 p.m.