Triple
T30383663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DTS Digital Surround |
E772892
|
entity |
| Predicate | maxBitrate |
P45737
|
FINISHED |
| Object | 1.5 Mbit/s on DVD-Video |
—
|
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: 1.5 Mbit/s on DVD-Video | Statement: [DTS Digital Surround, maxBitrate, 1.5 Mbit/s on DVD-Video]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxBitrate Context triple: [DTS Digital Surround, maxBitrate, 1.5 Mbit/s on DVD-Video]
-
A.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
B.
dvdVideoMaxBitrate
chosen
Indicates the maximum data transfer rate at which a DVD video stream can be encoded or played back.
-
C.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
D.
bluRayMaxBitrate
Indicates the maximum data transfer rate at which a Blu-ray disc or Blu-ray media stream can be encoded or played back.
-
E.
maxDataTransferMode
Indicates the data transfer mode in which the maximum possible data throughput is achieved between entities.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6851c44108190822e8d70e1114e09 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.