Triple
T28871471
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Message Service Element |
E732154
|
entity |
| Predicate | layeredAbove |
P164909
|
FINISHED |
| Object | DICOM Upper Layer Service for TCP/IP |
—
|
NE NERFINISHED |
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 Upper Layer Service for TCP/IP | Statement: [DICOM Message Service Element, layeredAbove, DICOM Upper Layer Service for TCP/IP]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: layeredAbove Context triple: [DICOM Message Service Element, layeredAbove, DICOM Upper Layer Service for TCP/IP]
-
A.
isLayeredOver
chosen
Indicates that one entity is positioned or arranged directly on top of another, partially or fully covering it in a layered manner.
-
B.
layerOf
Indicates that one entity forms a distinct layer or stratum of another entity within a structured or composite whole.
-
C.
sitsAbove
Indicates that one entity is positioned directly higher than and vertically over another entity.
-
D.
isTypicallyLayered
Indicates that something is usually composed of multiple distinct layers arranged one on top of another.
-
E.
imposedOn
Indicates that one party enforces, applies, or places a requirement, burden, or constraint onto another party or entity.
- 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.