Triple

T1776551
Position Surface form Disambiguated ID Type / Status
Subject DICOM standard E38992 entity
Predicate majorRevision P28684 FINISHED
Object DICOM 3.0 E38992 NE FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: DICOM 3.0 | Statement: [DICOM standard, majorRevision, DICOM 3.0]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: DICOM 3.0
Context triple: [DICOM standard, majorRevision, DICOM 3.0]
  • A. DICOM standard chosen
    The DICOM standard is a widely used international specification for handling, storing, transmitting, and displaying medical imaging information and related data.
  • B. DICOM Unique Identifier (UID)
    DICOM Unique Identifier (UID) is a globally unique numeric string used in medical imaging to unambiguously identify objects such as studies, series, images, and other DICOM entities.
  • C. DICOM Standards Committee
    The DICOM Standards Committee is the international body responsible for developing and maintaining the DICOM standard for medical imaging interoperability.
  • D. DICOM Application Entity
    A DICOM Application Entity is a networked software or device component in medical imaging systems that sends, receives, and processes DICOM messages and services for exchanging clinical data.
  • E. DCOM
    DCOM (Distributed Component Object Model) is a Microsoft technology that extends COM to support communication among software components over a network, enabling distributed, component-based applications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 batches)

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_69a8862e61708190af97b9838cc3f5de completed March 4, 2026, 7:21 p.m.
NER Named-entity recognition batch_69aa64b839608190b32bc041267458d5 completed March 6, 2026, 5:23 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5c96694819085f3ccafb141802f completed March 8, 2026, 5:45 p.m.
Created at: March 4, 2026, 7:31 p.m.