Triple
T32377506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVR-MS |
E827328
|
entity |
| Predicate | supportsStandardDefinition |
P206260
|
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: [DVR-MS, supportsStandardDefinition, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsStandardDefinition Context triple: [DVR-MS, supportsStandardDefinition, yes]
-
A.
supportsDisplayStandard
Indicates that one entity is compatible with and can correctly handle or render the specified display standard.
-
B.
standardDefinition
Indicates that something serves as the officially accepted or commonly recognized definition of a term or concept.
-
C.
supportsMobileTVStandard
Indicates that one entity is compatible with or implements a specified mobile TV broadcasting standard for use on mobile devices.
-
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.
videoStandard
Indicates the video format or broadcasting standard that applies to a given video or recording.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c9141dc819098d7fcc36e69882c |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379edf2d88190b492fca86ed23cac |
completed | May 12, 2026, 7:05 p.m. |
| PDg | Predicate description generation | batch_6a037c7fb9f88190b384b1b68200aef0 |
completed | May 12, 2026, 7:16 p.m. |
Created at: May 1, 2026, 12:51 a.m.