Triple
T14254425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NLM bibliographic services |
E353349
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical information system |
C16311
|
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 information system Context triple: [NLM bibliographic services, instanceOf, medical information system]
-
A.
medical system
A medical system is an organized framework of people, institutions, technologies, and processes that work together to deliver healthcare services for maintaining and improving individuals’ health.
-
B.
electronic health record system
An electronic health record system is a digital platform that securely collects, stores, manages, and shares patients’ health information to support clinical care, coordination, and decision-making.
-
C.
medical compendium
A medical compendium is a comprehensive, systematically organized reference work that consolidates medical knowledge, including diseases, treatments, diagnostics, and related scientific information, for use by healthcare professionals and students.
-
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.
health informatics organization
chosen
A health informatics organization is an entity that develops, manages, and applies information systems and data standards to improve the collection, exchange, analysis, and use of health information for clinical, administrative, and public health purposes.
- 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_69d8278c43e08190824146f4632b89a5 |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 10, 2026, 1:09 a.m.