Triple
T26887120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hoopla |
E677071
|
entity |
| Predicate | contentProtection |
P17307
|
FINISHED |
| Object | digital rights management |
—
|
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: digital rights management | Statement: [Hoopla, contentProtection, digital rights management]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contentProtection Context triple: [Hoopla, contentProtection, digital rights management]
-
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.
contentAccess
Indicates that one entity is permitted to retrieve, view, or otherwise use the content provided or controlled by another entity.
-
C.
contentLicense
Indicates the type of license or usage rights that govern how the associated content may be used, shared, or redistributed.
-
D.
contentLicenseRequires
Indicates that the terms of a content’s license obligate certain conditions, actions, or permissions to be met or granted when using that content.
-
E.
contentLicenseAllows
Indicates that a content license grants permission for a specified use or action involving the content.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c2f81c8190bf369226306eef09 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 27, 2026, 5:42 a.m.