Triple
T29938193
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GeForce 200 Series |
E760424
|
entity |
| Predicate | supportsHDCP |
P207196
|
FINISHED |
| Object | HDCP content protection |
—
|
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: HDCP content protection | Statement: [GeForce 200 Series, supportsHDCP, HDCP content protection]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsHDCP Context triple: [GeForce 200 Series, supportsHDCP, HDCP content protection]
-
A.
hasHDMIPort
Indicates that one entity (typically a device) is equipped with an HDMI port that can be used to connect to another entity.
-
B.
supportsDRMViaContainer
Indicates that one entity enables or provides digital rights management (DRM) functionality through the use of a specific container format or packaging mechanism.
-
C.
supportsHDRFormat
Indicates that one entity is capable of handling, displaying, or processing content encoded in a specified High Dynamic Range (HDR) format for another entity.
-
D.
supportsHDRStandard
Indicates that one entity is compatible with and can correctly handle or implement a specified HDR (High Dynamic Range) standard defined by another entity.
-
E.
supportsHEVC
Indicates that one entity provides compatibility with or the ability to handle HEVC (High Efficiency Video Coding) for another entity.
- 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_69f22463f3648190a603c3ff305c660b |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379e0f3d88190a4ee7b0673f1ef90 |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7ee0388190a29faeb5cdb0950a |
completed | May 12, 2026, 7:16 p.m. |
Created at: April 29, 2026, 6:21 p.m.