Triple
T28510089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Autopsy |
E721456
|
entity |
| Predicate | supportsImageType |
P24486
|
FINISHED |
| Object | raw disk 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: raw disk images | Statement: [Autopsy, supportsImageType, raw disk images]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsImageType Context triple: [Autopsy, supportsImageType, raw disk images]
-
A.
hasImageType
Indicates that an entity is associated with an image of a particular type or format.
-
B.
supportsJPEG
Indicates that one entity is capable of handling, displaying, or processing JPEG image files for another entity or in a given context.
-
C.
supportsType
chosen
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
-
D.
supportsRasterFormat
Indicates that one entity is capable of handling, processing, or outputting data in a specified raster image format.
-
E.
supportsHEIF
Indicates that one entity provides compatibility with or the ability to handle HEIF (High Efficiency Image File) format for another 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_69f01a5c072081908c7b04bcf6478da9 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_6a00c8e617548190bba4cdfbb6f512e0 |
completed | May 10, 2026, 6:05 p.m. |
| PD | Predicate disambiguation | batch_6a00c7e816b88190bd40f5ea2a768c8b |
completed | May 10, 2026, 6:01 p.m. |
Created at: April 28, 2026, 3:11 a.m.