Triple
T15263803
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CF Benchmarks |
E364848
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | financial index administrator |
C20303
|
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 index administrator Context triple: [CF Benchmarks, instanceOf, financial index administrator]
-
A.
financial index provider
chosen
A financial index provider is an organization that designs, calculates, maintains, and disseminates market indices used as benchmarks for investment products, performance measurement, and market analysis.
-
B.
financial market index
A financial market index is a statistical measure that tracks the performance of a specific group of securities, such as stocks or bonds, to represent the overall movement and value of a particular market or market segment.
-
C.
historical financial index
A historical financial index is a time-series measure that tracks and summarizes the past performance of a specific group of financial assets or markets over a defined historical period.
-
D.
index fund category
An index fund category is a classification of index-tracking investment funds grouped by the specific market index, asset class, region, or sector they are designed to replicate.
-
E.
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.
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
Created at: April 10, 2026, 3:14 a.m.