Triple
T8418722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM Application Entity |
E198793
|
entity |
| Predicate | exchangesDataType |
P82084
|
FINISHED |
| Object | DICOM images |
—
|
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 images | Statement: [DICOM Application Entity, exchangesDataType, DICOM images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: exchangesDataType Context triple: [DICOM Application Entity, exchangesDataType, DICOM images]
-
A.
exchanges
Indicates a reciprocal transfer of something of value between two or more entities.
-
B.
majorExchange
Indicates that an entity is a primary or significant trading venue where financial instruments are actively bought and sold.
-
C.
baseExchange
Indicates an exchange relationship where one entity serves as the base or reference for converting, trading, or swapping value with another.
-
D.
exchangeType
Indicates the kind or category of exchange occurring between entities, such as the method, direction, or nature of what is being traded or transferred.
-
E.
currencyInterchangeabilityAgreementSince
Indicates that two or more currencies have been mutually accepted as interchangeable under a formal agreement starting from a specified point in time.
- F. None of above. chosen
Provenance (4 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. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
| PDg | Predicate description generation | batch_69cb77690720819099de1e22b84a9563 |
completed | March 31, 2026, 7:27 a.m. |
Created at: March 30, 2026, 6:06 p.m.