Triple
T3078581
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Digital |
E64199
|
entity |
| Predicate | bluRayMaxBitrate |
P45738
|
FINISHED |
| Object | 640 kbit/s |
—
|
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: 640 kbit/s | Statement: [Dolby Digital, bluRayMaxBitrate, 640 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bluRayMaxBitrate Context triple: [Dolby Digital, bluRayMaxBitrate, 640 kbit/s]
-
A.
supportsHEVCEncode
Indicates that one entity provides the capability for another entity to perform HEVC (High Efficiency Video Coding) encoding.
-
B.
maximumResolution
Indicates the highest level of detail or fineness at which something (such as an image, display, or measurement) can be represented or processed.
-
C.
maximumBrightness
Indicates the highest level of brightness that an entity can reach or exhibit.
-
D.
supportsProResEncode
Indicates that one entity provides the capability for another entity to perform ProRes video encoding.
-
E.
supportsProResDecode
Indicates that one entity is capable of decoding or otherwise handling ProRes-encoded media for another entity or in a given context.
- 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_69ad857bb4c88190a4cf27893fcabed8 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada1a86a848190a47ca127cc7e6326 |
completed | March 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69ad9debb6308190be28378ae1fc98af |
completed | March 8, 2026, 4:03 p.m. |
| PDg | Predicate description generation | batch_69ada0f6fef48190b13898be383a246b |
completed | March 8, 2026, 4:16 p.m. |
Created at: March 8, 2026, 3:02 p.m.