Triple
T22029335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Survivors Insurance |
E544044
|
entity |
| Predicate | benefitTrigger |
P55857
|
FINISHED |
| Object | death of an insured worker |
—
|
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: death of an insured worker | Statement: [Survivors Insurance, benefitTrigger, death of an insured worker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: benefitTrigger Context triple: [Survivors Insurance, benefitTrigger, death of an insured worker]
-
A.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
B.
benefitAvailableAt
Indicates that a particular benefit can be obtained, accessed, or used at a specified location, time, or context.
-
C.
hasBenefit
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
D.
criterionForBenefits
chosen
Indicates that something serves as a condition or standard that must be met in order for an entity to receive certain benefits.
-
E.
benefitsCause
Indicates that one entity gains an advantage, improvement, or positive outcome as a result of another entity or cause.
- 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127ebf6d48190b84e7a45bbf9049c |
completed | April 28, 2026, 9:34 p.m. |
| PD | Predicate disambiguation | batch_69e6f63b0d048190b241622759aab9de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:24 p.m.