Triple
T28400376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | OC-3 |
E719379
|
entity |
| Predicate | bitRatePerChannel |
P54871
|
FINISHED |
| Object | 51.84 Mbit/s per STS-1 |
—
|
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: 51.84 Mbit/s per STS-1 | Statement: [OC-3, bitRatePerChannel, 51.84 Mbit/s per STS-1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitRatePerChannel Context triple: [OC-3, bitRatePerChannel, 51.84 Mbit/s per STS-1]
-
A.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
B.
mode2BitRate
chosen
Indicates the data transmission rate associated with a specific operational mode.
-
C.
audioSampleRateHz
Indicates the number of audio samples captured or played back per second, measured in hertz (Hz), for the associated audio data.
-
D.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
E.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64d6a679881909445372a0d5f75c4 |
completed | May 2, 2026, 7:15 p.m. |
| PD | Predicate disambiguation | batch_69f641e2f1708190b45b48d6a43c51d2 |
completed | May 2, 2026, 6:26 p.m. |
Created at: April 28, 2026, 1:19 a.m.