Triple

T13894712
Position Surface form Disambiguated ID Type / Status
Subject Speex E334057 entity
Predicate bitRateRange P110272 FINISHED
Object 2 kbps to 44 kbps 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: 2 kbps to 44 kbps | Statement: [Speex, bitRateRange, 2 kbps to 44 kbps]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bitRateRange
Context triple: [Speex, bitRateRange, 2 kbps to 44 kbps]
  • A. bitrateRange chosen
    Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
  • B. pegRate
    Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
  • C. mode2BitRate
    Indicates the data transmission rate associated with a specific operational mode.
  • D. maximumBitrate
    Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
  • 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_69d81c5dd2d48190b7a5fc1e009de936 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de23a741908190bdf46d76c5f1411a completed April 14, 2026, 11:23 a.m.
PD Predicate disambiguation batch_69dd464b1ab48190ae50bfc902bf6ef7 completed April 13, 2026, 7:38 p.m.
Created at: April 9, 2026, 10:15 p.m.