Triple

T28871779
Position Surface form Disambiguated ID Type / Status
Subject DICOM structured reports E732160 entity
Predicate hasSOPClassUIDType P79848 FINISHED
Object Structured Report Storage
Structured Report Storage is a DICOM service class that defines how structured clinical reports are encoded, stored, and exchanged in medical imaging systems.
 E732160 NE FINISHED

How this triple was built (3 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: Structured Report Storage | Statement: [DICOM structured reports, hasSOPClassUIDType, Structured Report Storage]
NEDg Description generation gpt-5.1
Instruction
Generate a one-sentence description of the target entity. 
You are given a context triple in the form (subject, predicate, object), where the object is the target entity. 
# Instructions
Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. 
Avoid repeating the information from the triple, unless really essential.
# Response Format
Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Structured Report Storage
Triple: [DICOM structured reports, hasSOPClassUIDType, Structured Report Storage]
Generated description
Structured Report Storage is a DICOM service class that defines how structured clinical reports are encoded, stored, and exchanged in medical imaging systems.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: hasSOPClassUIDType
Context triple: [DICOM structured reports, hasSOPClassUIDType, Structured Report Storage]
  • A. hasImagingType
    Indicates the specific imaging modality or technique associated with or used in a given imaging procedure or result.
  • B. hasStorageClass chosen
    Indicates that one entity is assigned or associated with a particular storage class that defines how its data is stored or managed.
  • C. hasStandardType
    Indicates that something conforms to or is categorized under a defined standard classification or type.
  • D. hasSymbologyType
    Indicates that an entity is associated with or classified under a particular type or category of symbology.
  • E. hasFeatureClass
    Indicates that an entity is associated with, or categorized under, a particular feature class that characterizes its type or nature.
  • F. None of above.

Provenance (6 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_69f05b06807c81909b4bbd4c20403a2b completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f70e8755a48190931eaa77946f9460 completed May 3, 2026, 8:59 a.m.
NED1 Entity disambiguation (via context triple) batch_6a24bbca11bc8190a5ca086b292bc308 completed June 7, 2026, 12:31 a.m.
NEDg Description generation batch_6a24c6cd18dc8190b5dd81a7443810ee completed June 7, 2026, 1:18 a.m.
NED2 Entity disambiguation (via description) batch_6a24c7444a28819093301b041d54b916 completed June 7, 2026, 1:20 a.m.
PD Predicate disambiguation batch_69f70abc00848190a1c3f495ef6c8dc6 completed May 3, 2026, 8:43 a.m.
Created at: April 28, 2026, 7:33 a.m.