Datasets:
answer stringlengths 2 697 | deep_reasoning stringlengths 175 534 | dialogue_history listlengths 3 65 | dialogue_id stringlengths 21 51 | domain stringclasses 14
values | id stringlengths 41 72 | is_high_quality bool 2
classes | metadata unknown | quality_flags listlengths 0 10 | quality_score float64 0 1 | source_dataset stringclasses 3
values | source_id stringlengths 11 40 | split stringclasses 1
value | streaming_chunks listlengths 3 65 | streaming_reasoning listlengths 3 65 | task_type stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
It is really a hot potato. | This sample contains safety-sensitive context. The reasoning should stay conservative, avoid amplifying sensitive details, and only support a safe, bounded assistant response. | [
{
"speaker": "user",
"text": "The taxi drivers are on strike again.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "What for?",
"turn_id": 2
},
{
"speaker": "user",
"text": "They want the government to reduce the price of the gasoline.",
"turn_id": 3
}
] | DailyDialog_test_000002 | travel | life_mt_sct_DailyDialog_test_000002_target4 | false | {
"category": "daily_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"shopping_retail"
],
"domain_category"... | [
"low_information_answer",
"mild_violence_or_conflict_context",
"sensitive_content"
] | 0.749 | DailyDialog | test_000002 | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the visible dialogue prefix is used. The turn is handled conservatively because the context is safety-sensitive, so the state keeps prior safe context and waits for a safe next response.",
"reasoning_confidence": "medium",
"reasoning_type": "safet... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the visible dialogue prefix is used. The turn is handled conservatively because the context is safety-sensitive, so the state keeps prior safe context and waits for a safe next response.",
"reasoning_confidence": "medium",
"reasoning_type": "safet... | prefix_to_next_assistant_text |
Ok how about Charlie Chan, located at Regent Street City Centre. Postcode is cb21db with a cheap price. Can I help you further today? | The visible history is a restaurant search task in travel transportation. It should track cuisine, area, and price. The answer should ask, confirm, or respond only to details present in the visible history. | [
{
"speaker": "user",
"text": "I'm looking for a local place to dine in the centre that serves chinese food.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "I have restaurants matching your criteria in all price ranges. Do you have a preference on price?",
"turn_id": 2
},
{
"... | MultiWOZ_PMUL0698.json | travel | life_mt_sct_MultiWOZ_PMUL0698.json_target4 | true | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"food_dini... | [
"weak_final_state"
] | 0.97 | MultiWOZ | PMUL0698.json | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | prefix_to_next_assistant_text |
So what days are you looking to fly? Hey, what else can you say? | The visible history is a flight booking task in travel transportation. Known constraints are destination=san francisco; origin=san francisco; transport_type=flight. The answer should address the booking or reservation step while tracking origin, destination, and travel dates. | [
{
"speaker": "user",
"text": "Hello. I'd like to find a round trip commercial airline flight from San Francisco to Denver.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "Hello, how can I help you? San Francisco to Denver, got it.",
"turn_id": 2
},
{
"speaker": "user",
"... | Taskmaster_dlg-00100680-00e0-40fe-8321-6d81b21bfc4f | travel | life_mt_sct_Taskmaster_dlg-00100680-00e0-40fe-8321-6d81b21bfc4f_target4 | false | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns",
"too_short_average_turn"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain... | [
"fragment_answer"
] | 0.499 | Taskmaster | dlg-00100680-00e0-40fe-8321-6d81b21bfc4f | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible taskmaster prefix is used. The user turn is treated as new task evidence; added slots: destination, origin, transport_type; changed slots: none; removed slots: none; new missing slots: none; resolved missing slots: none.",
"reasoni... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible taskmaster prefix is used. The user turn is treated as new task evidence; added slots: destination, origin, transport_type; changed slots: none; removed slots: none; new missing slots: none; resolved missing slots: none.",
"reasoni... | prefix_to_next_assistant_text |
What does that mean exactly? | The dialogue is workplace conversation in education career, with information request intent. The most recent user context is: Mainly because we've invested in a heat recovery system. The answer is grounded only in the visible dialogue history and should stay conservative. | [
{
"speaker": "user",
"text": "We've managed to reduce our energy consumption in our factory by about 15 per cent in the last two years.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "That's excellent. How have you managed that?",
"turn_id": 2
},
{
"speaker": "user",
"te... | DailyDialog_test_000003 | other_life | life_mt_sct_DailyDialog_test_000003_target4 | true | {
"category": "daily_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"education_career"
],
"domain_category... | [
"weak_final_state"
] | 0.899 | DailyDialog | test_000003 | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible dailydialog prefix is used. The user turn updates the daily dialogue context and response policy without relying on future turns; added slots: none; changed slots: none; removed slots: none. Unsupported slot evidence is suppressed for ... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible dailydialog prefix is used. The user turn updates the daily dialogue context and response policy without relying on future turns; added slots: none; changed slots: none; removed slots: none. Unsupported slot evidence is suppressed for ... | prefix_to_next_assistant_text |
Can I have more information for the train you're needing? Where are you departing from and arriving to? | The visible history is a train booking task in travel transportation. Known constraints are date_or_duration=sunday; transport_type=train. The answer should address the booking or reservation step while tracking departure, destination, and time constraints. | [
{
"speaker": "user",
"text": "I'm looking for a local place to dine in the centre that serves chinese food.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "I have restaurants matching your criteria in all price ranges. Do you have a preference on price?",
"turn_id": 2
},
{
"... | MultiWOZ_PMUL0698.json | travel | life_mt_sct_MultiWOZ_PMUL0698.json_target6 | true | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"food_dini... | [] | 1 | MultiWOZ | PMUL0698.json | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | prefix_to_next_assistant_text |
That sounds good, where you looking to go? That's right okay we have prices starting at $337. | The visible history is a flight booking task in travel transportation. Known constraints are date_or_duration=tonight, evening, 4 days; destination=san francisco; origin=san francisco; transport_type=flight. The answer should address the booking or reservation step while tracking origin, destination, and travel dates. | [
{
"speaker": "user",
"text": "Hello. I'd like to find a round trip commercial airline flight from San Francisco to Denver.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "Hello, how can I help you? San Francisco to Denver, got it.",
"turn_id": 2
},
{
"speaker": "user",
"... | Taskmaster_dlg-00100680-00e0-40fe-8321-6d81b21bfc4f | travel | life_mt_sct_Taskmaster_dlg-00100680-00e0-40fe-8321-6d81b21bfc4f_target6 | false | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns",
"too_short_average_turn"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain... | [
"weak_slot_evidence"
] | 0.749 | Taskmaster | dlg-00100680-00e0-40fe-8321-6d81b21bfc4f | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible taskmaster prefix is used. The user turn is treated as new task evidence; added slots: destination, origin, transport_type; changed slots: none; removed slots: none; new missing slots: none; resolved missing slots: none.",
"reasoni... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible taskmaster prefix is used. The user turn is treated as new task evidence; added slots: destination, origin, transport_type; changed slots: none; removed slots: none; new missing slots: none; resolved missing slots: none.",
"reasoni... | prefix_to_next_assistant_text |
What other sources of energy do you use? | The dialogue is workplace conversation in education career, with information request intent. The most recent user context is: Well, we use the exhaust gases from our printing presses to provide energy to heat our dryers. The answer is grounded only in the visible dialogue history and should stay conservative. | [
{
"speaker": "user",
"text": "We've managed to reduce our energy consumption in our factory by about 15 per cent in the last two years.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "That's excellent. How have you managed that?",
"turn_id": 2
},
{
"speaker": "user",
"te... | DailyDialog_test_000003 | other_life | life_mt_sct_DailyDialog_test_000003_target6 | true | {
"category": "daily_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"education_career"
],
"domain_category... | [
"weak_final_state"
] | 0.899 | DailyDialog | test_000003 | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible dailydialog prefix is used. The user turn updates the daily dialogue context and response policy without relying on future turns; added slots: none; changed slots: none; removed slots: none. Unsupported slot evidence is suppressed for ... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible dailydialog prefix is used. The user turn updates the daily dialogue context and response policy without relying on future turns; added slots: none; changed slots: none; removed slots: none. Unsupported slot evidence is suppressed for ... | prefix_to_next_assistant_text |
I have train TR1840 leaving at 16:36 is that okay? | The visible history is a train booking task in travel transportation. Known constraints are date_or_duration=sunday; destination=norwich; origin=cambridge; transport_type=train. The answer should address the booking or reservation step while tracking departure, destination, and time constraints. | [
{
"speaker": "user",
"text": "I'm looking for a local place to dine in the centre that serves chinese food.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "I have restaurants matching your criteria in all price ranges. Do you have a preference on price?",
"turn_id": 2
},
{
"... | MultiWOZ_PMUL0698.json | travel | life_mt_sct_MultiWOZ_PMUL0698.json_target8 | true | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"food_dini... | [] | 1 | MultiWOZ | PMUL0698.json | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | prefix_to_next_assistant_text |
Okay, Non-Stop and if I heard you correctly did you say you wanted to leave as early as possible and also Nile C. | The visible history is a flight booking task in travel transportation. Known constraints are date_or_duration=tonight, evening, 4 days; destination=san francisco; origin=san francisco; transport_type=flight. The answer should address the booking or reservation step while tracking origin, destination, and travel dates. | [
{
"speaker": "user",
"text": "Hello. I'd like to find a round trip commercial airline flight from San Francisco to Denver.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "Hello, how can I help you? San Francisco to Denver, got it.",
"turn_id": 2
},
{
"speaker": "user",
"... | Taskmaster_dlg-00100680-00e0-40fe-8321-6d81b21bfc4f | travel | life_mt_sct_Taskmaster_dlg-00100680-00e0-40fe-8321-6d81b21bfc4f_target8 | false | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns",
"too_short_average_turn"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain... | [
"weak_slot_evidence"
] | 0.749 | Taskmaster | dlg-00100680-00e0-40fe-8321-6d81b21bfc4f | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible taskmaster prefix is used. The user turn is treated as new task evidence; added slots: destination, origin, transport_type; changed slots: none; removed slots: none; new missing slots: none; resolved missing slots: none.",
"reasoni... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible taskmaster prefix is used. The user turn is treated as new task evidence; added slots: destination, origin, transport_type; changed slots: none; removed slots: none; new missing slots: none; resolved missing slots: none.",
"reasoni... | prefix_to_next_assistant_text |
Yes, Chinese people love drinking tea so much. Some even claim they can't live without tea. | The dialogue is uncertain context in general daily life, with planning coordination intent. The most recent user context is: Right. And China is the homeland of tea. The answer is grounded only in the visible dialogue history and should stay conservative. | [
{
"speaker": "user",
"text": "Believe it or not, tea is the most popular beverage in the world after water.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "Well, people from Asia to Europe all enjoy tea.",
"turn_id": 2
},
{
"speaker": "user",
"text": "Right. And China is... | DailyDialog_test_000004 | health_routine | life_mt_sct_DailyDialog_test_000004_target4 | false | {
"category": "daily_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"general_daily_lif... | [
"low_taxonomy_confidence",
"weak_final_state"
] | 0.749 | DailyDialog | test_000004 | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible dailydialog prefix is used. The user turn updates the daily dialogue context and response policy without relying on future turns; added slots: none; changed slots: none; removed slots: none.",
"reasoning_confidence": "medium",
... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible dailydialog prefix is used. The user turn updates the daily dialogue context and response policy without relying on future turns; added slots: none; changed slots: none; removed slots: none.",
"reasoning_confidence": "medium",
... | prefix_to_next_assistant_text |
You're all set. Reference number is NJB87PAP. Is there anything else I can help you with today? | The visible history is a train booking task in travel transportation. Known constraints are date_or_duration=sunday; destination=norwich; origin=cambridge; transport_type=train. The answer should address the booking or reservation step while tracking departure, destination, and time constraints. | [
{
"speaker": "user",
"text": "I'm looking for a local place to dine in the centre that serves chinese food.",
"turn_id": 1
},
{
"speaker": "assistant",
"text": "I have restaurants matching your criteria in all price ranges. Do you have a preference on price?",
"turn_id": 2
},
{
"... | MultiWOZ_PMUL0698.json | travel | life_mt_sct_MultiWOZ_PMUL0698.json_target10 | true | {
"category": "task_oriented_dialogue",
"category_taxonomy_method": "deterministic_source_aware_rules_v1",
"chunk_level": "turn",
"cleaning_flags": [
"too_many_turns"
],
"construction_type": "prefix_to_next_assistant_turn",
"deep_reasoning_method": "rule_based",
"domain_categories": [
"food_dini... | [] | 1 | MultiWOZ | PMUL0698.json | train | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | [
{
"chunk_id": "C1",
"reasoning": "After turn 1, only the current visible multiwoz prefix is used. The user turn is treated as new task evidence; added slots: none; changed slots: none; removed slots: none; new missing slots: destination; resolved missing slots: none.",
"reasoning_confidence": "high",
... | prefix_to_next_assistant_text |
LifeMultiTurnStreamingCoT
Version: v0.4 — Explicit Streaming Reasoning Release
LifeMultiTurnStreamingCoT is a text-to-text multi-turn life-domain dataset. Each row uses previous user-assistant dialogue turns as input, deterministic turn-level streaming state tracking as intermediate supervision, a compact final-state-based deep reasoning summary, and the next assistant turn as the answer.
This v0.4 release keeps the real DailyDialog, MultiWOZ 2.2, and Taskmaster sources while adding explicit turn-aligned streaming reasoning. No LLM calls are used for construction. The reasoning traces are deterministic rule-based annotations over visible dialogue prefixes and repaired state deltas.
Current Build Statistics
- Version: v0.4 — Explicit Streaming Reasoning Release
- Total rows: 30000
- Train rows: 24211
- Eval rows: 5789
- High-quality split rows: 17723
- High-quality train rows: 14339
- High-quality eval rows: 3384
- Average input turns: 9.705
- Average streaming chunks: 9.705
- Source distribution: {"DailyDialog": 10000, "MultiWOZ": 10000, "Taskmaster": 10000}
- Domain category distribution: {"customer_service": 204, "education_career": 2288, "finance_business": 180, "food_dining": 1262, "general_daily_life": 2881, "health_wellness": 221, "home_services": 226, "hospitality_lodging": 404, "personal_schedule": 688, "shopping_retail": 527, "social_relationship": 1984, "technology_support": 193, "travel_transportation": 18942}
- Intent category distribution: {"booking_or_reservation": 15758, "confirmation_clarification": 2710, "customer_support": 1241, "emotional_support": 232, "information_request": 6242, "instruction_following": 26, "negotiation_decision": 139, "planning_coordination": 1460, "problem_solving": 440, "recommendation": 739, "small_talk": 1013}
- Scenario category distribution: {"attraction_search": 455, "banking_support": 210, "customer_complaint": 218, "family_conversation": 600, "flight_booking": 9926, "food_ordering": 18, "friend_conversation": 456, "general_conversation": 3288, "home_repair": 101, "hotel_booking": 1557, "hotel_search": 184, "insurance_support": 95, "job_interview": 104, "medical_assistance": 291, "movie_ticketing": 218, "music_search": 141, "restaurant_booking": 1890, "restaurant_search": 819, "schedule_planning": 646, "school_life": 853, "shopping_assistance": 393, "taxi_booking": 1109, "technical_support": 453, "train_booking": 4317, "travel_planning": 253, "workplace_conversation": 1405}
- Taxonomy confidence distribution: {"high": 20506, "low": 2881, "medium": 6613}
- Quality tier distribution: {"bronze": 7505, "drop": 4772, "gold": 12479, "silver": 5244}
- Safety category distribution: {"safe": 28743, "sensitive": 1257}
- Target answer quality distribution: {"drop": 3924, "strong": 15129, "usable": 6819, "weak": 4128}
- Streaming reasoning quality distribution: {"strong": 14767, "usable": 15233}
- Streaming reasoning confidence distribution: {"high": 201954, "medium": 89194}
- Slot repair rows: 15233
- Suppressed slot reasons: {"generic_number_misread_as_budget": 36309, "percent_misread_as_budget": 13}
- Unknown/other taxonomy ratio: 0.0
- Category distribution: {"daily_dialogue": 10000, "task_oriented_dialogue": 20000}
Sources
- DailyDialog: daily multi-turn dialogue.
- MultiWOZ 2.2: multi-domain task-oriented dialogue.
- Taskmaster: real task-oriented dialogue from Taskmaster conversations.
Schema
Rows contain id, source_dataset, source_id, dialogue_id, domain, task_type, dialogue_history, streaming_chunks, top-level streaming_reasoning, deep_reasoning, answer, metadata, quality_flags, quality_score, is_high_quality, and split.
streaming_chunks[i] includes the original chunk fields plus state_before, state_update, state_after, state_delta, reasoning, reasoning_type, and reasoning_confidence. The top-level streaming_reasoning[i] list is aligned with streaming_chunks[i] by chunk_id and turn_id. The final schema remains unified across sources; source-specific details such as source, category, domain/services, scenario, original split, and raw file are kept in metadata.
Splits
train: training rows after deterministic dialogue-level split.eval: evaluation rows after deterministic dialogue-level split.high_quality: rows from train+eval whereis_high_qualityis true,quality_tieris gold/silver, safety is safe, and explicit streaming reasoning is strong/usable. Each high-quality row keepsmetadata.original_release_split.
Version History
v0.4 — Explicit Streaming Reasoning Release
- Added top-level
streaming_reasoningaligned withstreaming_chunks. - Added per-chunk
state_delta,reasoning,reasoning_type, andreasoning_confidence. - Added deterministic slot repair/suppression for unsupported visible-prefix slot evidence, including budget numeric misreads.
- Added
metadata.streaming_reasoning_method,metadata.has_explicit_streaming_reasoning,metadata.streaming_reasoning_quality,metadata.slot_repair_applied, andmetadata.suppressed_slots. - Added explicit reasoning quality flags and a
high_qualitysplit.
v0.3 — Safety and Grounding Quality Release
- Added safety/content filtering for training suitability.
- Added grounded slot extraction checks.
- Added target answer usefulness checks.
- Added taxonomy confidence and evidence fields.
- Added quality tiers: gold, silver, bronze, and drop.
- Updated
is_high_qualityto use quality tiers. - Removed or downgraded unsafe, ungrounded, malformed, or low-usefulness samples.
v0.2 — Taxonomy-Aware Quality Release
- Added
domain_category,intent_category, andscenario_category. - Added deterministic source-aware taxonomy rules.
- Improved category-aware quality thresholds.
- Reduced false penalties for long task-oriented dialogues.
v0.1 — Initial Real-Source Release
- Added real DailyDialog, MultiWOZ 2.2, and Taskmaster data.
- Built a balanced multi-source dataset with rule-based streaming/deep reasoning.
Category Taxonomy
Each sample includes a coarse metadata.category and three additional taxonomy fields:
metadata.domain_category: broad topic/domain such as travel, dining, lodging, entertainment, health, education, work, shopping, or general daily life.metadata.intent_category: interaction intent such as information request, recommendation, booking, planning, customer support, small talk, or emotional support.metadata.scenario_category: more specific scenario such as restaurant booking, hotel search, taxi booking, train booking, food ordering, movie ticketing, schedule planning, or workplace conversation.
The taxonomy is deterministic and source-aware. MultiWOZ uses domain/service annotations, Taskmaster uses scenario/file metadata when available, and DailyDialog uses lightweight keyword and dialogue-pattern rules. DailyDialog rows may have low taxonomy confidence when only weak keyword evidence is available.
Quality Metadata
Each row includes additional metadata fields:
metadata.safety_categorymetadata.safety_flagsmetadata.is_safe_for_trainingmetadata.grounding_flagsmetadata.slot_grounding_scoremetadata.has_grounding_issuemetadata.target_answer_flagsmetadata.target_answer_qualitymetadata.taxonomy_confidencemetadata.taxonomy_evidencemetadata.quality_tiermetadata.streaming_reasoning_methodmetadata.has_explicit_streaming_reasoningmetadata.streaming_reasoning_qualitymetadata.slot_repair_appliedmetadata.suppressed_slots
Recommended default training filter:
row["is_high_quality"] is True
and row["metadata"]["is_safe_for_training"] is True
and row["metadata"]["quality_tier"] in ["gold", "silver"]
and row["metadata"]["has_explicit_streaming_reasoning"] is True
and row["metadata"]["streaming_reasoning_quality"] in ["strong", "usable"]
Reasoning
Streaming reasoning is generated by deterministic rule-based state tracking over turn-level chunks. v0.4 explicit reasoning is generated only from visible prefix state, source metadata, repaired state deltas, and safety/taxonomy metadata. It does not call an LLM and does not rewrite the answer. DailyDialog rows focus on daily context and continuity. MultiWOZ and Taskmaster rows use task-oriented state changes, missing-slot status, and next-step policy. Deep reasoning is a compact global summary from the final tracked state, dialogue history, and target answer.
Quality Filtering
The quality checks are category-aware and include safety, grounding, target usefulness, explicit streaming reasoning quality, and tiering. Long task-oriented conversations are no longer penalized in the same way as short daily dialogues. Some heuristic checks, including weak final state and premature response detection, are kept as diagnostic warnings rather than hard filters.
quality_flags and metadata.quality_checks support filtering by real-source status, multi-turn context, non-empty reasoning, placeholder detection, category-aware length checks, malformed-row checks, repetition checks, grounding checks, safety checks, target-answer checks, explicit reasoning checks, and role alternation. Raw external data is not committed to git; processed train/eval/high_quality files are intended for upload to skyzhou06/LifeMultiTurnStreamingCoT.
Leakage Control
Train/eval splitting is performed by dialogue_id, so prefix samples from the same dialogue do not appear in both splits.
- Downloads last month
- 50