Triple
T26297093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Adobe Digital Editions |
E661445
|
entity |
| Predicate | supportsLibraryFormat |
P196140
|
FINISHED |
| Object | ACSM |
—
|
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: ACSM | Statement: [Adobe Digital Editions, supportsLibraryFormat, ACSM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsLibraryFormat Context triple: [Adobe Digital Editions, supportsLibraryFormat, ACSM]
-
A.
supportsBackupFormat
Indicates that one entity is capable of handling, storing, or operating with another entity as a backup data format.
-
B.
hasFileFormat
Indicates that one entity (typically a digital file or resource) is encoded, stored, or represented using a specific file format defined by the other entity.
-
C.
audioFormatSupported
Indicates that a particular audio format is recognized and can be correctly processed or played by a given system or component.
-
D.
supportsRasterFormat
Indicates that one entity is capable of handling, processing, or outputting data in a specified raster image format.
-
E.
supportsDiskImageFormat
Indicates that one entity is capable of handling, using, or being compatible with a specified disk image format.
- 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
| PDg | Predicate description generation | batch_69fe0d14778c8190986fa4f37f992a2f |
completed | May 8, 2026, 4:19 p.m. |
Created at: April 26, 2026, 10:13 p.m.