Triple
T1934706
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blu-ray Disc |
E41417
|
entity |
| Predicate | supportsContentProtection |
P203
|
FINISHED |
| Object | ROM-Mark |
—
|
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: ROM-Mark | Statement: [Blu-ray Disc, supportsContentProtection, ROM-Mark]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsContentProtection Context triple: [Blu-ray Disc, supportsContentProtection, ROM-Mark]
-
A.
usesDRM
Indicates that one entity applies digital rights management (DRM) controls or technologies to another entity (such as content, software, or media).
-
B.
protectsFeature
Indicates that one entity safeguards, preserves, or defends a particular feature or characteristic of another entity.
-
C.
protectionType
Indicates the kind or method of protection that is applied to or associated with an entity.
-
D.
supportsFeature
chosen
Indicates that one entity provides, enables, or is compatible with a particular feature or capability of another.
-
E.
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.
- 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_69a88649b24c819080047f26b6db2ded |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb29b51408190afb2f918814e68c7 |
completed | March 7, 2026, 5:07 a.m. |
| PD | Predicate disambiguation | batch_69abaff07cf88190b4883c5f17f90abd |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.