Triple
T8318217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HSB |
E194758
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | specialty insurer |
C19822
|
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: specialty insurer Context triple: [HSB, instanceOf, specialty insurer]
-
A.
property and casualty insurer
chosen
A property and casualty insurer is a company that provides insurance coverage to protect individuals and businesses against financial losses resulting from damage to property and legal liability for injuries or damage to others.
-
B.
specialized institution
A specialized institution is an organization dedicated to a specific field or function, providing focused services, expertise, or education within that domain.
-
C.
health insurance provider
A health insurance provider is an organization that offers and manages health coverage plans, collecting premiums and paying for or reimbursing members’ eligible medical expenses according to policy terms.
-
D.
specialized division
A specialized division is a distinct organizational unit focused on a specific function, expertise, or market segment to improve efficiency and effectiveness within a larger entity.
-
E.
special purpose entity
A special purpose entity is a legally separate organization created by a parent company to isolate financial risk, hold specific assets or liabilities, or conduct narrowly defined activities, often for financing or regulatory purposes.
- 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_69ca82e6e2648190a31eaf6f4f757b2a |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:55 p.m.