Triple
T22239655
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VDAX |
E549685
|
entity |
| Predicate | exchangeTradedProductsLinked |
P146869
|
FINISHED |
| Object | volatility derivatives |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: volatility derivatives | Statement: [VDAX, exchangeTradedProductsLinked, volatility derivatives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangeTradedProductsLinked Context triple: [VDAX, exchangeTradedProductsLinked, volatility derivatives]
-
A.
relatedExchange
Indicates that there is a connection or association between two exchanges or exchange-related events.
-
B.
isExchangeTraded
Indicates that the entity is traded on a formal exchange or marketplace rather than over-the-counter or privately.
-
C.
relatedTickerExchange
Indicates a relationship where a financial instrument’s ticker symbol is associated with the specific exchange on which it is listed or traded.
-
D.
exchanges
Indicates a reciprocal transfer of something of value between two or more entities.
-
E.
tradingLinks
Indicates that there are established trade or commercial exchange relationships between the referenced entities.
- F. None of above. chosen
Provenance (4 batches)
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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f132133b908190b0fb32a5ee68e1e6 |
completed | April 28, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
| PDg | Predicate description generation | batch_69e7222e74248190a2d3671049f117f2 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:38 p.m.