Triple
T31558525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | XAVC S-I |
E805193
|
entity |
| Predicate | bitrateType |
P171961
|
FINISHED |
| Object | high‑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: high‑bitrate | Statement: [XAVC S-I, bitrateType, high‑bitrate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitrateType Context triple: [XAVC S-I, bitrateType, high‑bitrate]
-
A.
bitrateOptions
Indicates the available or selected data transfer rates (bitrates) associated with a media stream or encoding configuration.
-
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.
bitrateAdaptationBasedOn
Indicates that the selection or adjustment of bitrate is determined based on the referenced factor or condition.
-
D.
bitstreamType
Indicates the specific format or category of a given bitstream within a digital system or data context.
-
E.
mode2BitRate
Indicates the data transmission rate associated with a specific operational mode.
- 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_69f348d22e088190ad555d5bd42f9da0 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a956e9b08190bf83547bba8e8147 |
completed | May 3, 2026, 1:48 a.m. |
| PD | Predicate disambiguation | batch_69f6a75656e081908739ed9e2f600e42 |
completed | May 3, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f6a8036ab481908019f2f071fa406e |
completed | May 3, 2026, 1:42 a.m. |
Created at: April 30, 2026, 10:14 p.m.