Triple
T35627750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J1939 |
E1029499
|
entity |
| Predicate | typicalBaudRate |
—
|
GENERATED |
| Object | 250 kbit/s |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalBaudRate Context triple: [J1939, typicalBaudRate, 250 kbit/s]
-
A.
definesNominalBaudRate
chosen
Indicates that an entity specifies the nominal (intended or standard) baud rate used for data transmission.
-
B.
basebandType
Indicates the type or category of baseband signal or processing used in a communication system.
-
C.
bandwidthCharacteristic
Indicates the relationship specifying the bandwidth-related properties or constraints associated with a connection, link, or communication channel.
-
D.
mode2BitRate
Indicates the data transmission rate associated with a specific operational mode.
-
E.
bitrateCharacteristic
Indicates the relationship between a media resource and the specific bitrate properties or constraints that characterize its encoding or transmission.
- F. None of above.
Provenance (1 batch)
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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:05 p.m.