Triple
T28871517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Upper Layer Protocol |
E732155
|
entity |
| Predicate | PDUType |
P70469
|
FINISHED |
| Object | A-ASSOCIATE-RQ PDU |
—
|
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: A-ASSOCIATE-RQ PDU | Statement: [DICOM Upper Layer Protocol, PDUType, A-ASSOCIATE-RQ PDU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: PDUType Context triple: [DICOM Upper Layer Protocol, PDUType, A-ASSOCIATE-RQ PDU]
-
A.
packetType
chosen
Indicates the specific category or kind of data packet involved in a communication or transmission.
-
B.
pdsType
Indicates that an entity has or is classified by a specific Product Data Specification (PDS) type or category.
-
C.
FECType
Indicates the classification of an entity according to the Federal Election Commission’s defined categories or types.
-
D.
protocolNumber
Indicates the specific identifying number assigned to a protocol that governs or documents an interaction, process, or agreement between entities.
-
E.
payloadType
Indicates the kind or category of payload associated with or carried by an entity or action.
- 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_69f65a47793481908efd891e27e541bf |
completed | May 2, 2026, 8:10 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 7:33 a.m.