Triple
T27561208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Deployment Imaging Servicing and Management |
E695772
|
entity |
| Predicate | supportsImageFormat |
P82508
|
FINISHED |
| Object | WIM |
—
|
NE NERFINISHED |
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: WIM | Statement: [Deployment Imaging Servicing and Management, supportsImageFormat, WIM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsImageFormat Context triple: [Deployment Imaging Servicing and Management, supportsImageFormat, WIM]
-
A.
supportsRasterFormat
Indicates that one entity is capable of handling, processing, or outputting data in a specified raster image 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.
supportsLibraryFormat
Indicates that one entity is capable of handling, using, or being compatible with a specified library format associated with another entity.
-
D.
supportsDiskImageFormat
chosen
Indicates that one entity is capable of handling, using, or being compatible with a specified disk 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_69ef5387e97c8190a9dab040d21cd048 |
completed | April 27, 2026, 12:16 p.m. |
| NER | Named-entity recognition | batch_69ff069ec1348190815375c5c9e38404 |
completed | May 9, 2026, 10:04 a.m. |
| PD | Predicate disambiguation | batch_69ff05ba57f88190a45d20f18044e0fb |
completed | May 9, 2026, 10 a.m. |
Created at: April 27, 2026, 1:39 p.m.