Triple
T1372784
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Hospital Life Insurance Company |
E30150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | life insurance company |
C972
|
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: life insurance company Context triple: [Massachusetts Hospital Life Insurance Company, instanceOf, life insurance company]
-
A.
company
A company is an organized entity, legally recognized or informally structured, that coordinates people and resources to produce goods or services for customers, typically in pursuit of profit or specific objectives.
-
B.
financial institution
chosen
A financial institution is an organization that manages money and financial services, such as accepting deposits, providing loans, facilitating investments, and enabling payment transactions for individuals, businesses, and governments.
-
C.
policy unit
A policy unit is an organizational entity responsible for researching, developing, analyzing, and coordinating policies to guide decision-making and strategic direction within an institution or government.
-
D.
public utility company
A public utility company is an organization, often government-regulated, that provides essential services such as electricity, water, gas, or telecommunications to the public, typically operating as a natural monopoly to ensure reliable and widespread access.
-
E.
telecommunications company
A telecommunications company is an organization that provides communication services such as voice, data, and video transmission over wired or wireless networks to individuals and businesses.
- 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_69a498f912008190a376a98b207b2071 |
completed | March 1, 2026, 7:52 p.m. |
Created at: March 1, 2026, 7:57 p.m.