Triple
T35627681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CANopen |
E1029498
|
entity |
| Predicate | supportsBitRate |
P175991
|
FINISHED |
| Object | 10 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: 10 kbit/s | Statement: [CANopen, supportsBitRate, 10 kbit/s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBitRate Context triple: [CANopen, supportsBitRate, 10 kbit/s]
-
A.
hasBasicRateBitrate
chosen
Indicates that an entity is associated with a fundamental or default data transmission bitrate value.
-
B.
bitrateRange
Indicates the range of data transfer rates (minimum to maximum bitrate) within which something, such as a media stream or encoding, operates.
-
C.
bitrateType
Indicates the type or category of bitrate used in an encoding or transmission (e.g., constant, variable, or adaptive).
-
D.
bitrateCharacteristic
Indicates the relationship between a media resource and the specific bitrate properties or constraints that characterize its encoding or transmission.
-
E.
supportsBandwidths
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
- 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_69f76e07bb0c8190968ea2d836fc42c9 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a04d8348190a4819666eab42c9b |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:05 p.m.