Triple
T22539032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Solvency I regime |
E557234
|
entity |
| Predicate | policyholderProtectionLevel |
P15826
|
FINISHED |
| Object | basic |
—
|
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: basic | Statement: [Solvency I regime, policyholderProtectionLevel, basic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyholderProtectionLevel Context triple: [Solvency I regime, policyholderProtectionLevel, basic]
-
A.
benefitProtection
Indicates that one entity provides protective advantages or safeguards that benefit another entity.
-
B.
policyLevel
Indicates the degree or tier of strictness, scope, or priority associated with a given policy.
-
C.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
D.
protectionType
chosen
Indicates the kind or method of protection that is applied to or associated with an entity.
-
E.
policyName
Indicates the specific name or title assigned to a policy associated with an 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_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.