Triple
T12534585
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orthanc |
E299654
|
entity |
| Predicate | supportsProtocol |
P203
|
FINISHED |
| Object |
DICOM C-STORE
DICOM C-STORE is a core DICOM network service used to transmit and store medical imaging objects between systems such as modalities, PACS, and archives.
|
E990007
|
NE FINISHED |
How this triple was built (4 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 C-STORE | Statement: [Orthanc, supportsProtocol, DICOM C-STORE]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DICOM C-STORE Context triple: [Orthanc, supportsProtocol, DICOM C-STORE]
-
A.
DICOMweb STOW-RS
DICOMweb STOW-RS is a web-based DICOM service that enables clients to store medical imaging studies and related data over HTTP using RESTful APIs.
-
B.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
C.
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.
-
D.
DICOM PS3.7 Message Exchange
DICOM PS3.7 Message Exchange is the part of the DICOM standard that defines how medical imaging systems structure, manage, and communicate messages to exchange clinical data reliably between application entities.
-
E.
DICOM PS3.5 Data Structures and Encoding
DICOM PS3.5 Data Structures and Encoding is the part of the DICOM standard that defines how medical imaging information is formatted, encoded, and structured for reliable storage and exchange between systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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: DICOM C-STORE Triple: [Orthanc, supportsProtocol, DICOM C-STORE]
Generated description
DICOM C-STORE is a core DICOM network service used to transmit and store medical imaging objects between systems such as modalities, PACS, and archives.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: DICOM C-STORE Target entity description: DICOM C-STORE is a core DICOM network service used to transmit and store medical imaging objects between systems such as modalities, PACS, and archives.
-
A.
DICOMweb STOW-RS
DICOMweb STOW-RS is a web-based DICOM service that enables clients to store medical imaging studies and related data over HTTP using RESTful APIs.
-
B.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
C.
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.
-
D.
DICOM PS3.7 Message Exchange
DICOM PS3.7 Message Exchange is the part of the DICOM standard that defines how medical imaging systems structure, manage, and communicate messages to exchange clinical data reliably between application entities.
-
E.
DICOM PS3.5 Data Structures and Encoding
DICOM PS3.5 Data Structures and Encoding is the part of the DICOM standard that defines how medical imaging information is formatted, encoded, and structured for reliable storage and exchange between systems.
- F. None of above. chosen
Provenance (5 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_69d6ada5cdd48190860d9ce30aff69be |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d9546d3b2081908d3e0659f8f13678 |
completed | April 10, 2026, 7:50 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f65577e3388190b6c1c2e8dee7f6ac |
completed | May 2, 2026, 7:50 p.m. |
| NEDg | Description generation | batch_69f6566e7bf88190a33c609caf9b4f3d |
completed | May 2, 2026, 7:54 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f65799ca588190b9f7a07f5c1a842c |
completed | May 2, 2026, 7:59 p.m. |
Created at: April 8, 2026, 9:57 p.m.