Triple
T1870453
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | LOINC |
E39023
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical terminology standard |
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: medical terminology standard Context triple: [LOINC, instanceOf, medical terminology standard]
-
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.
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.
-
C.
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.
-
D.
medical academic department
A medical academic department is an organizational unit within a medical school or academic health center responsible for education, research, and clinical services in a specific medical specialty or discipline.
-
E.
metadata standard
A metadata standard is a structured set of rules and definitions that specify how information about resources should be described, formatted, and shared to ensure consistency, interoperability, and discoverability.
- 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_69a8862f7074819096afe7fe65e179e9 |
completed | March 4, 2026, 7:21 p.m. |
Created at: March 4, 2026, 7:34 p.m.