Triple
T7847269
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Title V Revenue Offsets |
E181953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | HIPAA title |
C23014
|
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: HIPAA title Context triple: [Title V Revenue Offsets, instanceOf, HIPAA title]
-
A.
section of the Affordable Care Act
A section of the Affordable Care Act is a distinct, numbered subdivision of the federal health reform law that sets forth specific legal requirements, definitions, or provisions governing health insurance and related programs.
-
B.
title of the Social Security Act
The title of the Social Security Act is the formal, legally designated name or heading that identifies the statute establishing the Social Security program and its related provisions.
-
C.
title of the Code of Federal Regulations
The title of the Code of Federal Regulations is the top-level organizational division that groups together all federal regulations pertaining to a broad subject area, such as labor, environment, or transportation.
-
D.
health insurance law
Health insurance law is the body of legal rules and regulations that governs the creation, coverage, administration, and enforcement of health insurance policies and the rights and obligations of insurers, providers, and insured individuals.
-
E.
healthcare interoperability initiative
A healthcare interoperability initiative is a coordinated effort to enable seamless, secure exchange and use of health data across diverse systems, organizations, and technologies to improve care quality, efficiency, and patient outcomes.
- F. None of above. chosen
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_69ca8285d6488190a95d4c02d7354b53 |
completed | March 30, 2026, 2:02 p.m. |
Created at: March 30, 2026, 4:49 p.m.