Triple
T20657932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3by |
E507675
|
entity |
| Predicate | definesSignalingRate |
P44387
|
FINISHED |
| Object | 25.78125 Gbaud |
—
|
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: 25.78125 Gbaud | Statement: [IEEE 802.3by, definesSignalingRate, 25.78125 Gbaud]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesSignalingRate Context triple: [IEEE 802.3by, definesSignalingRate, 25.78125 Gbaud]
-
A.
signalingMode
Indicates the method or mechanism by which one entity communicates or transmits signals to another.
-
B.
usesSignaling
Indicates that one entity communicates or coordinates with another by emitting, transmitting, or interpreting signals.
-
C.
usesSignalingChannel
Indicates that one entity communicates or exchanges information with another through a specific signaling channel or medium.
-
D.
definesNominalBaudRate
chosen
Indicates that an entity specifies the nominal (intended or standard) baud rate used for data transmission.
-
E.
usesBalancedSignaling
Indicates that an entity employs a signaling strategy in which opposing or complementary signals are used in a coordinated, proportionate way to maintain balance in communication or control.
- 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_69e0b4bf58c081908e52a4500e03ff83 |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6b2eefd5c8190a71d4be690a6ae0e |
completed | April 20, 2026, 11:12 p.m. |
| PD | Predicate disambiguation | batch_69e5c0315f5081908098707c6455e56e |
completed | April 20, 2026, 5:57 a.m. |
Created at: April 16, 2026, 11:43 a.m.