Triple
T31119533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Financial Services Compensation Scheme |
E793185
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | investor compensation scheme |
C36697
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: investor compensation scheme Context triple: [Financial Services Compensation Scheme, instanceOf, investor compensation scheme]
-
A.
cooperative risk-sharing scheme
A cooperative risk-sharing scheme is a collaborative arrangement in which participants pool resources or contributions to collectively absorb and distribute individual losses, reducing the financial impact of adverse events on any single member.
-
B.
colonial investor
A colonial investor is an individual or entity that allocates capital to enterprises, infrastructure, or resource extraction in colonized or colonizing territories, seeking profit from imperial expansion and control.
-
C.
technical commission system
A technical commission system is a structured framework of processes, tools, and governance used to plan, execute, verify, and document the commissioning and performance validation of technical systems or facilities.
-
D.
deposit insurance scheme
chosen
A deposit insurance scheme is a system, typically run or backed by a government or central authority, that guarantees bank customers will be repaid their deposits up to a specified limit if their financial institution fails.
-
E.
value investor
A value investor is an individual who seeks to buy securities that appear undervalued based on fundamental analysis, aiming to profit as the market eventually recognizes their true worth.
- F. None of above.
Provenance (1 batch)
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_69f224d0a7688190af3fe3e6e26d01ed |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:04 p.m.