Triple
T28871982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Frame of Reference |
E732165
|
entity |
| Predicate | hasAttributeName |
P34760
|
FINISHED |
| Object | Frame of Reference UID |
—
|
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: Frame of Reference UID | Statement: [DICOM Frame of Reference, hasAttributeName, Frame of Reference UID]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAttributeName Context triple: [DICOM Frame of Reference, hasAttributeName, Frame of Reference UID]
-
A.
usesAttribute
Indicates that one entity employs, relies on, or makes use of a specific attribute of another entity in performing an action or defining a relationship.
-
B.
hasFieldName
chosen
Indicates that one entity is associated with, or identified by, a specific field name in a data structure or schema.
-
C.
hasAttributeUsage
Indicates that an entity uses or applies a particular attribute in some context or manner.
-
D.
holdsAttribute
Indicates that one entity possesses, exhibits, or is characterized by a particular attribute or property.
-
E.
hasLocalName
Indicates that an entity is known by a specific name or designation within a particular local language, script, or regional context.
- 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_69f65f7731e4819099d5bd3d915ee266 |
completed | May 2, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 7:33 a.m.