Triple
T1407307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolby Digital 5.1 |
E31722
|
entity |
| Predicate | typicalBitrateRange |
P1376
|
FINISHED |
| Object | 384–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: 384–640 kbit/s | Statement: [Dolby Digital 5.1, typicalBitrateRange, 384–640 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBitrateRange Context triple: [Dolby Digital 5.1, typicalBitrateRange, 384–640 kbit/s]
-
A.
typicalRuntimeRange
Indicates the usual lower and upper bounds of time typically required for an entity to run or complete its operation.
-
B.
typicalRange
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
C.
dataRate
chosen
Indicates the rate at which data is transmitted, processed, or transferred between entities over a given time interval.
-
D.
typicalRecordingDuration
Indicates the usual or standard length of time that something is recorded.
-
E.
pegRatio
Indicates the relationship between a company’s price-to-earnings (P/E) ratio and its expected earnings growth rate, expressing how highly the market values each unit of anticipated growth.
- 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_69a49918e1f88190ba610f9dc8114578 |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c3be10348190ade8a73780d2c008 |
completed | March 1, 2026, 10:54 p.m. |
| PD | Predicate disambiguation | batch_69a4bf030a388190bc82d30b9233e873 |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.