Triple
T8418613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Standards Committee |
E198791
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medical imaging standards body |
C3871
|
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 imaging standards body Context triple: [DICOM Standards Committee, instanceOf, medical imaging standards body]
-
A.
technical standards body
A technical standards body is an organization that develops, maintains, and promotes agreed-upon technical specifications and protocols to ensure interoperability, safety, and consistency across industries and technologies.
-
B.
medical organization
A medical organization is an entity that coordinates healthcare services, resources, and professionals to promote, maintain, or restore people’s health.
-
C.
standards-setting organization
chosen
A standards-setting organization is an entity that develops, maintains, and promotes agreed-upon technical, professional, or procedural norms to ensure compatibility, quality, and interoperability across industries or sectors.
-
D.
joint commission
A joint commission is a temporary or permanent body formed by representatives from two or more organizations, governments, or parties to collaboratively oversee, regulate, or resolve issues of shared concern.
-
E.
healthcare accreditation organization
A healthcare accreditation organization is an independent body that evaluates and certifies healthcare providers and institutions against established quality and safety standards to ensure consistent, high-quality patient care.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:06 p.m.