Triple
T28470844
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | STS-1 |
E720431
|
entity |
| Predicate | hasOverheadBitRate |
P45736
|
FINISHED |
| Object | 1.728 Mbit/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: 1.728 Mbit/s | Statement: [STS-1, hasOverheadBitRate, 1.728 Mbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOverheadBitRate Context triple: [STS-1, hasOverheadBitRate, 1.728 Mbit/s]
-
A.
hasMaxMacroblocksPerSecond
Indicates the maximum number of macroblocks that can be processed or handled per second in a given context.
-
B.
supportsRobustLowBitrateModes
Indicates that something is capable of operating effectively and reliably at low data bitrates, maintaining acceptable performance or quality under such constrained conditions.
-
C.
maximumBitrate
chosen
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
D.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
E.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
- 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_69f01a5983f48190b7c1b8857245a4f7 |
completed | April 28, 2026, 2:24 a.m. |
| NER | Named-entity recognition | batch_69f64ee1c4d08190ba95b02f3aa0ca67 |
completed | May 2, 2026, 7:22 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 2:48 a.m.