Triple
T22539025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvency I regime |
E557234
|
entity |
| Predicate | supersededBecauseOf |
P56544
|
FINISHED |
| Object | need for more risk-based supervision |
—
|
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: need for more risk-based supervision | Statement: [Solvency I regime, supersededBecauseOf, need for more risk-based supervision]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supersededBecauseOf Context triple: [Solvency I regime, supersededBecauseOf, need for more risk-based supervision]
-
A.
wasSupersededBy
Indicates that one entity has been replaced or made obsolete by another entity that takes over its role or function.
-
B.
replacedBecause
chosen
Indicates that one entity has been substituted for another specifically due to a particular reason or cause.
-
C.
supersededSpecificationIn
Indicates that one specification has been replaced or made obsolete by another specification within a given context or system.
-
D.
supersededInPrecisionBy
Indicates that one entity’s level of precision has been replaced or overtaken by another entity’s greater precision.
-
E.
discontinuedInFavorOf
Indicates that one thing has been stopped, ended, or phased out specifically so it can be replaced by another preferred alternative.
- 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_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. |
Created at: April 16, 2026, 8:51 p.m.