Triple
T22239660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VDAX |
E549685
|
entity |
| Predicate | riskMeasureType |
P15871
|
FINISHED |
| Object | market risk |
—
|
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: market risk | Statement: [VDAX, riskMeasureType, market risk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskMeasureType Context triple: [VDAX, riskMeasureType, market risk]
-
A.
riskMeasure
Indicates a quantitative assessment of the level of risk associated with an entity, event, or situation.
-
B.
riskType
chosen
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
C.
riskModel
Indicates a relationship where an entity serves as or is associated with a model used to assess, quantify, or manage risk for another entity or situation.
-
D.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
E.
riskFeature
Indicates that one entity possesses or exhibits a characteristic, condition, or attribute that increases the likelihood or severity of a negative outcome for another entity or situation.
- 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_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. |
Created at: April 16, 2026, 8:38 p.m.