Triple
T22539019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvency I regime |
E557234
|
entity |
| Predicate | riskSensitivity |
P148587
|
FINISHED |
| Object | low |
—
|
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: low | Statement: [Solvency I regime, riskSensitivity, low]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riskSensitivity Context triple: [Solvency I regime, riskSensitivity, low]
-
A.
riskAttitude
Indicates how an entity’s preferences or behavior change in response to uncertainty, reflecting its tendency to avoid, accept, or seek risk in decisions.
-
B.
riskType
Indicates the category or nature of risk associated with an entity, event, or relationship.
-
C.
riskBasis
Indicates the underlying factor, condition, or rationale that forms the basis for assessing or assigning risk in a given context.
-
D.
riskTaken
Indicates that an entity has undertaken an action or decision involving exposure to potential loss, harm, or uncertainty.
-
E.
riskBelief
Indicates that an entity holds a belief or assessment about the likelihood or severity of a potential risk associated with another entity, event, or situation.
- 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_69e11e58662081909ae346ab384514ca |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15f302cd4819098c97ca4fa96363e |
completed | April 29, 2026, 1:30 a.m. |
| PD | Predicate disambiguation | batch_69e898c864148190a3f5feec7967d49c |
completed | April 22, 2026, 9:45 a.m. |
| PDg | Predicate description generation | batch_69e8aa3b4c288190951cca06d42bea51 |
completed | April 22, 2026, 11 a.m. |
Created at: April 16, 2026, 8:51 p.m.