Triple
T8240439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DSM-III-R |
E192520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | diagnostic classification manual |
C1782
|
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: diagnostic classification manual Context triple: [DSM-III-R, instanceOf, diagnostic classification manual]
-
A.
clinical reference classification
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.
-
B.
medical classification system
chosen
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.
-
C.
canonical classification
Canonical classification is a standardized method of organizing entities into universally recognized categories based on their essential, defining characteristics.
-
D.
survey-based classification system
A survey-based classification system is a framework that categorizes individuals, groups, or entities into defined segments based on their responses to structured questionnaires or assessments.
-
E.
health classification system
A health classification system is a structured framework used to categorize and code health-related conditions, statuses, and services for consistent recording, analysis, and decision-making.
- 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_69ca82dc8f148190a2c75a98501a7b91 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:47 p.m.