Triple
T23010777
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RBC Insurance |
E572899
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | insurance company division |
C47132
|
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: insurance company division Context triple: [RBC Insurance, instanceOf, insurance company division]
-
A.
reinsurance company division
A reinsurance company division is an organizational unit within a reinsurance firm responsible for managing specific lines of business, geographic regions, or functional activities such as underwriting, risk assessment, and client relationships.
-
B.
insurance group
An insurance group is a collection of related insurance companies under common ownership or control that coordinate to offer a range of insurance products and services.
-
C.
insurance pioneer
An insurance pioneer is an individual or organization that introduces groundbreaking concepts, practices, or technologies that fundamentally reshape how risk is assessed, priced, and managed within the insurance industry.
-
D.
asset management company division
A division of an asset management company is an organizational unit responsible for managing specific types of investment products, client segments, or geographic markets within the broader firm.
-
E.
banking division
A banking division is an organizational unit within a financial institution responsible for managing specific banking services, customer segments, or product lines to achieve targeted financial and strategic objectives.
- F. None of above. chosen
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_69e245b764cc8190a51be76f1d9611e1 |
completed | April 17, 2026, 2:37 p.m. |
Created at: April 17, 2026, 3:51 p.m.