Synthetic Packing Lists Dataset (Syn-Item-Lists)

A synthetic, expert-quality dataset of travel packing lists designed specifically for fine-tuning travel logistics assistants, recommendation systems, and structured-output LLMs.

Manually curating comprehensive packing lists that adapt to highly specific travel conditions (like climate, infrastructure, and active risks) is a massive bottleneck. To solve this, this dataset was generated using knowledge distillation via Google Gemini, grounded tightly on 10 hand-curated, gold-standard seed examples.

Unlike naive synthetic data, this dataset utilizes a hierarchical sampling framework to ensure that every scenario is logistically realistic and structurally sound.

🔗 External Resources

• Hugging Face Repository: rinad12/Syn-Item-Lists

📐 Dataset Structure & Schema

All records are stored in a single file: dataset.jsonl (2,200 records, balanced ~equally across all 22 trip intents).

Each line is a self-contained JSON record consisting of an input travel context and a flat output list of recommended items.

Input Schema (The Context)

Field	Type	Description
intent	String	Trip purpose — one of 22 categories (e.g. "Hiking / Trekking", "Business trip")
duration	Integer	Trip length in days (range: 1–90, intent-aware — e.g. Business trip: 1–5, Digital nomad relocation: 14–90)
infrastructure	String	Availability of utilities/services at the destination — one of 12 levels (e.g. "Basic — rural / remote village")
climate	String	Climate type at the destination — one of 14 types (e.g. "Subtropical (hot humid summer)")
risks	List[String]	1–3 active risk factors drawn from 18 options (e.g. "Vector-borne disease (mosquitoes / ticks)", "High UV exposure")
max_items	Integer	Upper bound on the list length, computed per-scenario and passed to the model as a hard constraint

Output Schema (The Packing List)

Field	Type	Description
item	String	Highly specific item name (e.g. "Merino Wool Socks", instead of just "Socks")
quantity	Integer	Number of units recommended to pack
reason	String	Concise justification of why the item is needed (max 10 words)

JSON Example

{
  "input": {
    "intent": "Wildlife safari",
    "duration": 10,
    "infrastructure": "Basic — rural / remote village",
    "climate": "Subtropical (hot humid summer)",
    "risks": ["Vector-borne disease (mosquitoes / ticks)", "High UV exposure"],
    "max_items": 13
  },
  "output": [
    {
      "item": "Long-Sleeved Lightweight Shirt",
      "quantity": 5,
      "reason": "Barrier against mosquitoes at dawn/dusk drives."
    },
    {
      "item": "DEET Insect Repellent",
      "quantity": 2,
      "reason": "Essential protection against vector-borne disease."
    }
  ]
}

⚙️ How the Data Was Generated

To maintain exceptionally high data quality and avoid "hallucinated" or nonsensical travel scenarios, the generation pipeline utilizes several strict guardrails:

1. Hierarchical Dependency Sampling: Scenarios are constructed top-down: Intent → Infrastructure → Climate → Risks. Each level only samples from a curated pool of plausible options for the level above it, so you never see impossible combinations, like a corporate business trip requiring a tent in an Arctic tundra.

2. Intent-Aware Durations: Trip lengths are drawn from logical, intent-specific ranges (e.g. Business trips: 1–5 days; Digital Nomad relocations: 14–90 days); intents without an explicit range fall back to a weighted 1–90 day distribution.

3. Balanced Intent Representation: Samples are generated from a shuffled intent queue so every intent gets equal representation regardless of total sample count.

4. Dynamic List Caps: The max_items field is mathematically constrained using a base duration tier, modified by the intent type (e.g. Camping adds items, Business trip subtracts items), and padded with a risk floor (len(risks) + 3).

5. Strict Schema Enforcement: Every sample was generated using Gemini's native response_schema feature with a Pydantic model, meaning zero malformed JSON outputs — invalid responses are skipped and regenerated automatically.

💡 Potential Use Cases

• LLM Fine-Tuning: Ideal for instruction-tuning smaller open-source models (like LLaMA, Mistral, or Qwen) to handle highly constrained, structured JSON generation tasks.

• Travel Recommendation Systems: Training classification or embedding models to suggest hyper-specific gear based on user-input metadata.

• RAG Evaluation: Testing retrieval-augmented generation pipelines on how well they adjust recommendations to dynamic risk and climate factors.

Domain coverage

22 trip intents: Beach vacation · Camping / Backpacking · Business trip · City sightseeing · Hiking / Trekking · Ski / Snowboard · Road trip · Volunteer mission · Extreme tourism · Scientific research expedition · Digital nomad relocation · Humanitarian aid mission · Photography expedition · Spiritual pilgrimage · Competitive sports event · Formal event / Destination wedding · Medical tourism · Language immersion program · Culinary tourism · Wildlife safari · Festival attendance · Academic / Study abroad

12 infrastructure levels: from off-grid wilderness to luxury all-inclusive resort, including underground cave systems, high-altitude research stations, and marine/live-aboard environments

14 climate types: tropical rain · arid desert · arctic · high altitude · temperate · Mediterranean · maritime · monsoonal · subpolar/tundra · subtropical · continental · coastal fog · volcanic/geothermal · equatorial rainforest

18 risk factors: including high UV exposure · avalanche risk · vector-borne disease · civil instability · extreme wildlife encounters · altitude sickness · frostbite/hypothermia · food safety/contamination · flash floods · and more

Limitations

• All data is synthetic — generated by an LLM and not validated by human travel experts or field professionals.
• Item quantities are model-generated heuristics, not empirically verified.
• Coverage is biased toward the 22 predefined trip intents and 18 risk factors used during generation.
• The dataset is English-only.

📜 License

This dataset is open-source and licensed under the Apache 2.0 License. Feel free to use it for both commercial and research purposes!