Triple
T29999221
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM prefix "DICM" |
E762114
|
entity |
| Predicate | hasCharacterSequence |
P191352
|
FINISHED |
| Object | DICM |
—
|
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: DICM | Statement: [DICOM prefix "DICM", hasCharacterSequence, DICM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCharacterSequence Context triple: [DICOM prefix "DICM", hasCharacterSequence, DICM]
-
A.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
B.
hasCharacters
Indicates that an entity (such as a work or story) includes or features certain characters as part of its content.
-
C.
hasRecurringCharacterFrom
Indicates that one work or series includes a character who also appears recurrently in another work or series.
-
D.
containsCharacter
Indicates that one entity includes a specific character as part of its content or composition.
-
E.
isSequence
Indicates that one entity is an ordered list or succession of elements arranged in a specific, meaningful order.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fcdf2394748190b35cead3e208447d |
completed | May 7, 2026, 6:51 p.m. |
| PD | Predicate disambiguation | batch_69fcdbe344ec8190a0471911952f4b82 |
completed | May 7, 2026, 6:37 p.m. |
| PDg | Predicate description generation | batch_69fcdf22ab8881908b257f16522920c5 |
completed | May 7, 2026, 6:51 p.m. |
Created at: April 29, 2026, 6:40 p.m.