Triple
T17923585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBBO |
E448134
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | securities market benchmark |
C20755
|
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: securities market benchmark Context triple: [NBBO, instanceOf, securities market benchmark]
-
A.
financial market benchmark family
A financial market benchmark family is a structured group of related indices or reference rates designed to measure and compare the performance, risk, or pricing of specific segments of financial markets under a common methodology.
-
B.
commodity benchmark
A commodity benchmark is a standardized reference price or index used to measure the value and performance of a specific commodity or group of commodities in markets and contracts.
-
C.
financial market index
chosen
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.
-
D.
interest rate benchmark
An interest rate benchmark is a standardized reference rate, typically derived from the average rates at which major financial institutions lend to one another, used to set or compare interest rates on various financial products and contracts.
-
E.
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.
- 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.