Triple
T25217938
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VIX futures |
E631877
|
entity |
| Predicate | notionalValueDependsOn |
P101951
|
FINISHED |
| Object | contract multiplier |
—
|
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: contract multiplier | Statement: [VIX futures, notionalValueDependsOn, contract multiplier]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notionalValueDependsOn Context triple: [VIX futures, notionalValueDependsOn, contract multiplier]
-
A.
amountDependsOn
chosen
Indicates that the quantity or magnitude of one entity is determined by, or varies as a function of, another entity.
-
B.
contingentOn
Indicates that the occurrence, validity, or outcome of one event or condition depends on the fulfillment or existence of another.
-
C.
monetaryValue
Indicates the amount of money associated with an entity, event, or transaction.
-
D.
valuedBy
Indicates that one entity is regarded as important, useful, or held in high esteem by another entity.
-
E.
isValuedFor
Indicates that one entity is appreciated, esteemed, or considered important because of a particular quality, contribution, or characteristic it provides to another entity.
- F. None of above.
Provenance (3 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_69e75a8d1aa48190a4320acd3654762c |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f47b907f6081908c6c0e33f4cae736 |
completed | May 1, 2026, 10:08 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:59 p.m.