Triple
T26297039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobo Nia |
E661444
|
entity |
| Predicate | supportsAdobeDRM |
P17307
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kobo Nia, supportsAdobeDRM, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsAdobeDRM Context triple: [Kobo Nia, supportsAdobeDRM, yes]
-
A.
supportsDRMViaContainer
Indicates that one entity enables or provides digital rights management (DRM) functionality through the use of a specific container format or packaging mechanism.
-
B.
usesDRM
chosen
Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
-
C.
hasDedicatedMediaKeys
Indicates that an input device includes specific keys assigned to control media functions (such as play, pause, volume, or track navigation).
-
D.
supportsDigitalDownloads
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
-
E.
supportsH264
Indicates that one entity provides compatibility with, or the ability to encode/decode or process, H.264 video 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_69ee812cd48c81908054068f545f0526 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69fddf721c1481909301a0f379368f10 |
completed | May 8, 2026, 1:04 p.m. |
| PD | Predicate disambiguation | batch_69fddda1ae7c8190b5848ff9a9e39826 |
completed | May 8, 2026, 12:57 p.m. |
Created at: April 26, 2026, 10:13 p.m.