Triple
T17922176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICE Global Network |
E448099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | market data infrastructure platform |
C6450
|
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: market data infrastructure platform Context triple: [ICE Global Network, instanceOf, market data infrastructure platform]
-
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.
energy trading software platform
An energy trading software platform is a digital system that enables market participants to analyze prices, manage positions, execute and settle trades, and monitor risk across power, gas, and other energy markets.
-
C.
charting platform
A charting platform is a software system that enables users to create, customize, and interact with visual representations of data for analysis and decision-making.
-
D.
financial data platform
chosen
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.
-
E.
financial market identifier registry
A financial market identifier registry is a centralized system that assigns, maintains, and provides standardized unique identifiers for financial markets, venues, and related entities to support accurate reference, trading, and regulatory reporting.
- 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_69d8b9f6d394819082a6d69fd1e23d2f |
completed | April 10, 2026, 8:51 a.m. |
Created at: April 10, 2026, 10:20 a.m.