Triple
T22041559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Extra Help program |
E544647
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | prescription drug cost assistance program |
C45716
|
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: prescription drug cost assistance program Context triple: [Extra Help program, instanceOf, prescription drug cost assistance program]
-
A.
reimbursement program
A reimbursement program is a structured system through which individuals or organizations are repaid for eligible expenses they have incurred, typically after submitting proof of payment and meeting predefined criteria.
-
B.
prescription drug
A prescription drug is a regulated medication that can only be legally obtained and used under the authorization of a licensed healthcare provider to diagnose, treat, or prevent specific medical conditions.
-
C.
prescription medication
A prescription medication is a regulated drug that can only be obtained with authorization from a licensed healthcare provider to diagnose, treat, or prevent specific medical conditions.
-
D.
drug donation program
A drug donation program is an organized initiative through which pharmaceutical products are provided at low or no cost to eligible populations or health systems to improve access to essential medicines.
-
E.
drug development support program
A drug development support program is a structured set of services, resources, and guidance designed to assist researchers and companies in efficiently advancing drug candidates from discovery through preclinical and clinical development to regulatory approval.
- 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_69e11e32445c8190ab97089b48a130bb |
completed | April 16, 2026, 5:36 p.m. |
Created at: April 16, 2026, 8:25 p.m.