Triple
T15537117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wii optical disc |
E370375
|
entity |
| Predicate | copyProtection |
P15826
|
FINISHED |
| Object | proprietary encryption |
—
|
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: proprietary encryption | Statement: [Wii optical disc, copyProtection, proprietary encryption]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: copyProtection Context triple: [Wii optical disc, copyProtection, proprietary encryption]
-
A.
coreProtection
Indicates that an entity provides essential safeguarding or defense for another entity’s central or most critical component.
-
B.
protectionType
chosen
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
-
D.
usesDRM
Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
-
E.
protectsFeature
Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of 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_69d85cc521a08190921fb50319dddc34 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e0442f3c688190a599165e526af2ed |
completed | April 16, 2026, 2:06 a.m. |
| PD | Predicate disambiguation | batch_69deda7a95c48190bbe29fadcf17191a |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:06 a.m.