Triple
T6034217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RTCRtpEncodingParameters |
E134377
|
entity |
| Predicate | propertyType_maxBitrate |
P45736
|
FINISHED |
| Object | unsigned long |
—
|
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: unsigned long | Statement: [RTCRtpEncodingParameters, propertyType_maxBitrate, unsigned long]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: propertyType_maxBitrate Context triple: [RTCRtpEncodingParameters, propertyType_maxBitrate, unsigned long]
-
A.
maximumBitrate
chosen
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
B.
bluRayMaxBitrate
Indicates the maximum data transfer rate at which a Blu-ray disc or Blu-ray media stream can be encoded or played back.
-
C.
dvdVideoMaxBitrate
Indicates the maximum data transfer rate at which a DVD video stream can be encoded or played back.
-
D.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
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_69c00875db5c819099dd5bb833ec43c2 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c056b220608190b156be95632cf3b3 |
completed | March 22, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69c049e9a68c81909da0cfe4779ce9b5 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:08 p.m.