omi_transcript_segments

6 rows where conversation_id = "23771581-6fc1-4da2-b574-9800a9639763"

✎ View and edit SQL

This data as json, CSV (advanced)

Suggested facets: speaker_id, speaker_name

id ▼ conversation_id text speaker_id speaker_name start_time end_time
21963 User Briefly Describes Feeling Depressed 23771581-6fc1-4da2-b574-9800a9639763 It's up fork stuff. 0 User 3.077698238485027e-07 1.0400303077698254
21964 User Briefly Describes Feeling Depressed 23771581-6fc1-4da2-b574-9800a9639763 Barely. 0 User 43.13006030776978 43.69006030776973
21965 User Briefly Describes Feeling Depressed 23771581-6fc1-4da2-b574-9800a9639763 Okay. 1 Speaker 1 67.63006030776978 68.59009030776974
21966 User Briefly Describes Feeling Depressed 23771581-6fc1-4da2-b574-9800a9639763 But now now often can 0 User 68.59009030776974 71.23003030776977
21967 User Briefly Describes Feeling Depressed 23771581-6fc1-4da2-b574-9800a9639763 I'm down. I'm very down. I'm very depressed. 0 User 82.98999030776974 84.98999030776974
21968 User Briefly Describes Feeling Depressed 23771581-6fc1-4da2-b574-9800a9639763 How are you doing? How are you? 0 User 100.30003030776982 103.52003030776973

Advanced export

JSON shape: default, array, newline-delimited, object

CSV options: 

CREATE TABLE omi_transcript_segments (
    id INTEGER PRIMARY KEY AUTOINCREMENT,
    conversation_id TEXT NOT NULL,
    text TEXT,
    speaker_id INTEGER,
    speaker_name TEXT,
    start_time REAL,
    end_time REAL,
    FOREIGN KEY (conversation_id) REFERENCES omi_conversations(id)
);
CREATE INDEX idx_omi_segments_conv ON omi_transcript_segments(conversation_id);