Triple
T28620125
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MPEG-DASH |
E724357
|
entity |
| Predicate | bitrateAdaptationBasedOn |
P164949
|
FINISHED |
| Object | available bandwidth |
—
|
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: available bandwidth | Statement: [MPEG-DASH, bitrateAdaptationBasedOn, available bandwidth]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitrateAdaptationBasedOn Context triple: [MPEG-DASH, bitrateAdaptationBasedOn, available bandwidth]
-
A.
mediaAdaptationSettingOf
Indicates that a media adaptation (such as a film, series, or game) is set in the narrative world or environment of a particular original work.
-
B.
trackAdaptation
Indicates that one entity monitors, records, or follows changes in another entity’s adaptation or adjustment over time.
-
C.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
D.
hasMediaAdaptation
Indicates that a work has been adapted into another medium, such as film, television, or other forms of media.
-
E.
isAdaptation
Indicates that one work is derived from, based on, or reinterprets the content of another work.
- 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6562fd3488190be1acd8c526a28d2 |
completed | May 2, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69f651aad92c8190b874b3b5f9f64434 |
completed | May 2, 2026, 7:34 p.m. |
| PDg | Predicate description generation | batch_69f652a3a8208190a4fdd66f34138bd2 |
completed | May 2, 2026, 7:38 p.m. |
Created at: April 28, 2026, 4:33 a.m.