Triple
T25534600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | AZW |
E640008
|
entity |
| Predicate | oftenDRMProtected |
P17307
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [AZW, oftenDRMProtected, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: oftenDRMProtected Context triple: [AZW, oftenDRMProtected, true]
-
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.
hasLegalDepositRightFor
Indicates that an entity holds the legal right to receive, collect, or claim deposited materials (such as publications or documents) from another entity under legal deposit regulations.
-
C.
isProtectedInSomeRegions
Indicates that the entity is subject to legal or formal protection in at least one geographic region or jurisdiction.
-
D.
hasDigitalDistribution
Indicates that something is made available or delivered through electronic or online channels rather than through physical media.
-
E.
supportsDigitalDownloads
Indicates that one entity enables or allows the other entity to provide or access digital file downloads.
- 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_69e75dbf3f9c8190b3f2a75d1b75d127 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 3:16 p.m.