Triple
T24269619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | S&P Global Broad Market Index Series |
E605240
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stock market index series |
C19754
|
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: stock market index series Context triple: [S&P Global Broad Market Index Series, instanceOf, stock market index series]
-
A.
equity index series
chosen
An equity index series is a time-ordered set of calculated index values that track the aggregated performance of a defined group of equities according to a consistent methodology.
-
B.
stock market index code
A stock market index code is a standardized alphanumeric identifier used to uniquely represent a specific stock market index for trading, tracking, and reference purposes.
-
C.
stock market index segment
A stock market index segment is a defined subset of an overall stock index that groups together constituent securities based on shared characteristics such as sector, size, geography, or investment style to enable more targeted analysis and benchmarking.
-
D.
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.
-
E.
financial indexing platform
A financial indexing platform is a system that aggregates, calculates, and maintains market or custom financial indices, providing real-time and historical index data for analysis, benchmarking, and investment products.
- 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_69e2954707dc8190915551eb114cfff6 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:07 a.m.