Triple
T9532557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VT100 |
E229930
|
entity |
| Predicate | supportsBaudRatesUpTo |
P48289
|
FINISHED |
| Object | 19200 bps |
—
|
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: 19200 bps | Statement: [VT100, supportsBaudRatesUpTo, 19200 bps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsBaudRatesUpTo Context triple: [VT100, supportsBaudRatesUpTo, 19200 bps]
-
A.
supportsBusSpeed
Indicates that one entity is capable of operating at, or is compatible with, a specified bus communication speed of another entity.
-
B.
supportsBandwidths
chosen
Indicates that an entity is compatible with or can operate using the specified range or set of bandwidth values.
-
C.
definesNominalBaudRate
Indicates that an entity specifies the nominal (intended or standard) baud rate used for data transmission.
-
D.
supportsSpeedControls
Indicates that an entity provides or is compatible with mechanisms to adjust or control speed.
-
E.
mode2BitRate
Indicates the data transmission rate associated with a specific operational mode.
- 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_69ca8479934c81908006d0e6e970ae05 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd98b5651881908241b040f123c6a8 |
completed | April 1, 2026, 10:14 p.m. |
| PD | Predicate disambiguation | batch_69cca56c44f88190a54a5d2a133bb07e |
completed | April 1, 2026, 4:56 a.m. |
Created at: March 30, 2026, 8 p.m.