Triple
T27708478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HIPAA Omnibus Rule |
E698614
|
entity |
| Predicate | expandsLiabilityTo |
P94284
|
FINISHED |
| Object | business associates |
—
|
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: business associates | Statement: [HIPAA Omnibus Rule, expandsLiabilityTo, business associates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: expandsLiabilityTo Context triple: [HIPAA Omnibus Rule, expandsLiabilityTo, business associates]
-
A.
liabilityType
Indicates the specific category or nature of liability associated with an entity, obligation, or financial exposure.
-
B.
establishesLiabilityFor
Indicates that one party is held legally responsible or accountable for a particular act, omission, or outcome.
-
C.
expandedProtectionTo
Indicates that an existing protection, safeguard, or coverage was broadened to include an additional entity, group, area, or scope.
-
D.
expandsRegulationTo
chosen
Indicates that an existing regulation is being broadened in scope to cover additional subjects, activities, or jurisdictions.
-
E.
carrierLiabilityType
Indicates the specific type or category of legal or contractual liability that a carrier assumes in relation to the goods or services it transports or provides.
- 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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 27, 2026, 3:01 p.m.