Triple
T2745566
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harold Shipman |
E60857
|
entity |
| Predicate | wholeLifeTariff |
P24161
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Harold Shipman, wholeLifeTariff, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wholeLifeTariff Context triple: [Harold Shipman, wholeLifeTariff, true]
-
A.
maximumLifetimeBenefit
Indicates the greatest total amount of benefit that can be received over the entire duration of eligibility or coverage.
-
B.
isForLife
chosen
Indicates that something is intended to last or remain valid for the entire duration of a person’s or entity’s life.
-
C.
guaranteeCoverage
Indicates that one party commits to providing financial or protective coverage for another party or specified situation.
-
D.
insuranceType
Indicates the specific category or kind of insurance coverage associated with an entity or relationship.
-
E.
insurance
Indicates a relationship where one party provides financial protection or coverage to another against specified risks or losses, typically in exchange for payment.
- 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_69ab4b79846081909096725374d65ce9 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdb4d37a481908cc2ad4666f3ac94 |
completed | March 7, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69abd829f1e88190aab1d54f87c69714 |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:56 p.m.