Triple
T28871676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Print Management Service Class |
E732159
|
entity |
| Predicate | usesCommunicationModel |
P30779
|
FINISHED |
| Object | DICOM SCU-SCP model |
—
|
LITERAL 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 SCU-SCP model | Statement: [Print Management Service Class, usesCommunicationModel, DICOM SCU-SCP model]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesCommunicationModel Context triple: [Print Management Service Class, usesCommunicationModel, DICOM SCU-SCP model]
-
A.
usedToCommunicate
Indicates that one entity serves as a medium or tool through which another entity conveys information, messages, or signals.
-
B.
communicationModel
chosen
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
C.
hasCommunicationUse
Indicates that something is used for, or serves the purpose of, communication.
-
D.
designedToCommunicate
Indicates that something has been intentionally created or configured for the purpose of conveying information or messages to others.
-
E.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
- F. None of above.
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_69f05b06807c81909b4bbd4c20403a2b |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 7:33 a.m.