Triple
T4689653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Editions |
E104003
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | health terminology artifact |
C14885
|
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: health terminology artifact Context triple: [National Editions, instanceOf, health terminology artifact]
-
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.
healthcare interoperability initiative
A healthcare interoperability initiative is a coordinated effort to enable seamless, secure exchange and use of health data across diverse systems, organizations, and technologies to improve care quality, efficiency, and patient outcomes.
-
C.
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.
-
D.
health publication
chosen
A health publication is a periodical or digital resource that provides researched, evidence-based information on medical, wellness, and public health topics for professionals or the general public.
-
E.
Patient Care Device integration profile
The Patient Care Device integration profile defines how medical devices and healthcare information systems communicate and exchange data to ensure accurate, timely, and interoperable patient monitoring and therapy management.
- 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_69bd43df91f481908e9add1b617b60ef |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:16 p.m.