Triple
T4238982
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | G.722 |
E94763
|
entity |
| Predicate | mode2BitRate |
P54871
|
FINISHED |
| Object | 56 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: 56 kbit/s | Statement: [G.722, mode2BitRate, 56 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mode2BitRate Context triple: [G.722, mode2BitRate, 56 kbit/s]
-
A.
pegRate
Indicates a fixed or controlled exchange rate at which one currency is pegged to another or to a reference value.
-
B.
maximumBitrate
Indicates the highest data transfer rate allowed or supported for a given media stream or connection.
-
C.
modeBDescription
Indicates the descriptive label or explanation associated with a specific operational or behavioral mode B.
-
D.
definesNominalBaudRate
Indicates that an entity specifies the nominal (intended or standard) baud rate used for data transmission.
-
E.
duplexMode
Indicates whether a communication link or device operates in half-duplex or full-duplex mode, defining if data can flow in one or both directions simultaneously.
- 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_69b34537cc6481909cd0a96acbb33ef7 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b34e76b6e0819084d0ce137b5ba74e |
completed | March 12, 2026, 11:38 p.m. |
| PD | Predicate disambiguation | batch_69b347f587148190a1830503459939b6 |
completed | March 12, 2026, 11:10 p.m. |
| PDg | Predicate description generation | batch_69b34e04ef1c81908bb34ae1cbfab1e6 |
completed | March 12, 2026, 11:36 p.m. |
Created at: March 12, 2026, 11:05 p.m.