Triple
T29999220
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DICOM prefix "DICM" |
E762114
|
entity |
| Predicate | hasByteLength |
P84681
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [DICOM prefix "DICM", hasByteLength, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasByteLength Context triple: [DICOM prefix "DICM", hasByteLength, 4]
-
A.
hasFieldLength
Indicates that an entity possesses a field whose length (such as number of characters or size) is specified or constrained.
-
B.
hasMaximumLength
Indicates that there is an upper limit on the length or size of something, beyond which it cannot extend.
-
C.
hasMaxLengthApprox
Indicates that something has a maximum length that is approximately equal to a specified value, allowing for some tolerance or imprecision.
-
D.
hasFixedLength
chosen
Indicates that the related entity possesses a length that is constant and does not change.
-
E.
hasLengthRange
Indicates that an entity’s length falls within a specified minimum-to-maximum range.
- 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_69f2246a47ac81909cf5213053687ffc |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69f6794cf5848190a60ca2c4d9f50098 |
completed | May 2, 2026, 10:23 p.m. |
| PD | Predicate disambiguation | batch_69f66ec9919881908a187bfc7c4df192 |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 29, 2026, 6:40 p.m.