Triple
T4751178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SNOMED CT Browser |
E105479
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | clinical terminology browser |
C1036
|
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: clinical terminology browser Context triple: [SNOMED CT Browser, instanceOf, clinical terminology browser]
-
A.
historical medical term
A historical medical term is an outdated or obsolete word or phrase once used in medicine to describe diseases, conditions, treatments, or anatomical concepts that have since been redefined, replaced, or discredited.
-
B.
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.
-
C.
controlled vocabulary
chosen
A controlled vocabulary is a standardized, curated set of terms and phrases used consistently to describe and organize information, ensuring uniformity and improving search and retrieval.
-
D.
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.
-
E.
medical condition group
A medical condition group is a categorized collection of related diseases or disorders that share common characteristics, causes, affected systems, or treatment approaches.
- 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_69bd43f07fa48190954317d01600994a |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:20 p.m.