Triple
T5842383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clearstream |
E129623
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | post-trade services provider |
C11345
|
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: post-trade services provider Context triple: [Clearstream, instanceOf, post-trade services provider]
-
A.
financial market infrastructure company
chosen
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.
sell-side platform provider
A sell-side platform provider offers technology and services that enable publishers and content owners to manage, optimize, and automate the sale of their advertising inventory to buyers across digital channels.
-
C.
investment management software provider
An investment management software provider develops and delivers digital tools that help financial professionals and institutions plan, execute, monitor, and optimize investment portfolios and related operations.
-
D.
industry clearing and settlement system
An industry clearing and settlement system is a centralized infrastructure that validates, nets, and finalizes financial transactions between market participants, ensuring accurate, timely, and risk-managed transfer of funds and securities.
-
E.
wealthtech platform
A wealthtech platform is a digital solution that leverages technology to help individuals and institutions manage, grow, and optimize their investments and overall financial wealth.
- 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_69c0084bd31c8190a796bb6284845e83 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:54 p.m.