Triple
T8418760
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Unique Identifier |
E198794
|
entity |
| Predicate | usedToIdentify |
P9157
|
FINISHED |
| Object | DICOM Series |
E198794
|
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 Series | Statement: [DICOM Unique Identifier, usedToIdentify, DICOM Series]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DICOM Series Context triple: [DICOM Unique Identifier, usedToIdentify, DICOM Series]
-
A.
DICOM standard
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)
chosen
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 Part 10: Media Storage and File Format
DICOM Part 10: Media Storage and File Format is the section of the DICOM standard that defines how medical images and related data are encapsulated, structured, and stored in files for exchange and archiving across different systems.
-
D.
DICOMweb
DICOMweb is a web-based standard for accessing, storing, and exchanging medical imaging data over HTTP using RESTful services.
-
E.
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.
- 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_69ca8312d63c8190bf133b676b44a385 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb84c7d6e48190a2bbde89c5d42af6 |
completed | March 31, 2026, 8:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ce033df9c48190a8ec6b9347ba6e81 |
completed | April 2, 2026, 5:48 a.m. |
Created at: March 30, 2026, 6:06 p.m.