Triple
T17799218
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.723.1 |
E444376
|
entity |
| Predicate | bitRateOption |
P54871
|
FINISHED |
| Object | 5.3 kbit/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: 5.3 kbit/s | Statement: [G.723.1, bitRateOption, 5.3 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bitRateOption Context triple: [G.723.1, bitRateOption, 5.3 kbit/s]
-
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.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
D.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
E.
referenceRate
Indicates that one entity serves as the benchmark or base rate used to determine or adjust the rate applied to another entity or transaction.
- 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_69d8b9efe370819095cd219b143ae727 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e487fe19dc8190b7e9dc96f39e0861 |
completed | April 19, 2026, 7:45 a.m. |
| PD | Predicate disambiguation | batch_69e3d8de28688190844b65acf6af54e6 |
completed | April 18, 2026, 7:17 p.m. |
Created at: April 10, 2026, 10:13 a.m.