Triple
T24929081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Windows Media |
E618937
|
entity |
| Predicate | usesDRMTechnology |
P17307
|
FINISHED |
| Object | Windows Media DRM |
—
|
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: Windows Media DRM | Statement: [Windows Media, usesDRMTechnology, Windows Media DRM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDRMTechnology Context triple: [Windows Media, usesDRMTechnology, Windows Media DRM]
-
A.
usesDRM
chosen
Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
-
B.
supportsDisplayTechnology
Indicates that one entity is compatible with, or capable of operating using, a specified display technology.
-
C.
hasDedicatedMediaKeys
Indicates that an input device includes specific keys assigned to control media functions (such as play, pause, volume, or track navigation).
-
D.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
E.
supportsPhysicalMedia
Indicates that one entity provides the capability to use, read, or handle physical media formats (such as discs, tapes, or printed materials) associated with 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_69e2fab9edd88190b86004a78a28bc20 |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f464b4c9b0819085daa00c7c3b8b76 |
completed | May 1, 2026, 8:30 a.m. |
| PD | Predicate disambiguation | batch_69f45cf017a88190b4985b11159c907d |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 18, 2026, 5:29 a.m.