Triple
T32062213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Opus |
E818774
|
entity |
| Predicate | supportsBitrateType |
P171961
|
FINISHED |
| Object | constant bitrate |
—
|
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: constant bitrate | Statement: [Opus, supportsBitrateType, constant bitrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBitrateType Context triple: [Opus, supportsBitrateType, constant bitrate]
-
A.
bitrateType
chosen
Indicates the type or category of bitrate used in an encoding or transmission (e.g., constant, variable, or adaptive).
-
B.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
C.
hasBasicRateBitrate
Indicates that an entity is associated with a fundamental or default data transmission bitrate value.
-
D.
bitrateOptions
Indicates the available or selected data transfer rates (bitrates) associated with a media stream or encoding configuration.
-
E.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
- 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_69f348fdacec8190b9f74375ca3b2094 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a0379eaa540819095a1c5d9f3513f9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 12:22 a.m.