Triple
T22690118
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A10BJ05 |
E561028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pharmacologic classification code |
C1785
|
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: pharmacologic classification code Context triple: [A10BJ05, instanceOf, pharmacologic classification code]
-
A.
medical classification system
A medical classification system is an organized framework that categorizes diseases, conditions, procedures, and related health information using standardized codes to support diagnosis, treatment, research, and healthcare administration.
-
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.
clinical reference classification
chosen
A clinical reference classification is a structured system that organizes medical concepts, diagnoses, procedures, or other health-related information into standardized categories to support consistent documentation, analysis, and communication in healthcare.
-
E.
pharmaceutical drug
A pharmaceutical drug is a chemically defined substance or combination of substances administered to diagnose, treat, prevent, or alleviate disease or medical conditions in humans or animals.
- F. None of above.
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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:13 p.m.