Triple
T33791290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Family Heritage Life Insurance Company of America |
E865936
|
entity |
| Predicate | policyholderType |
P94712
|
FINISHED |
| Object | individuals |
—
|
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: individuals | Statement: [Family Heritage Life Insurance Company of America, policyholderType, individuals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: policyholderType Context triple: [Family Heritage Life Insurance Company of America, policyholderType, individuals]
-
A.
typeOfInsurer
Indicates the specific category or classification of an insurer in relation to an insurance policy or coverage.
-
B.
personType
chosen
Indicates that an entity is classified as a particular type or category of person.
-
C.
payerType
Indicates the type or category of entity responsible for making a payment in the relationship.
-
D.
insuranceType
Indicates the specific category or kind of insurance coverage associated with an entity or relationship.
-
E.
insuredParties
Indicates that certain entities are covered or protected under an insurance policy or agreement.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: May 1, 2026, 1:45 a.m.