Triple
T632821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BBC iPlayer |
E15957
|
entity |
| Predicate | usesDRM |
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: [BBC iPlayer, usesDRM, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDRM Context triple: [BBC iPlayer, usesDRM, yes]
-
A.
hasDigitalAccess
Indicates that an entity has the ability or permission to use or access digital resources, services, or information.
-
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.
hasLegalDeposit
Indicates that an entity is required to deposit copies of its published material with a designated legal deposit institution or repository.
-
D.
allowsProprietaryDerivativeWorks
Indicates that one party grants permission for others to create and distribute derivative works that may be kept proprietary rather than shared under the same open terms.
-
E.
hasDigitalForm
Indicates that something exists or is available in a digital or electronic 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_69a4935c131c8190a5378c6bf101e8cc |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a49ec2a4c08190bc5c6ce8a10b0967 |
completed | March 1, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69a49d030c648190ba1a02301b45f694 |
completed | March 1, 2026, 8:09 p.m. |
| PDg | Predicate description generation | batch_69a49defe58c8190bd39ef47c9f660a7 |
completed | March 1, 2026, 8:13 p.m. |
Created at: March 1, 2026, 7:35 p.m.