saturn

This dataset catalogs 7,130 world languages, each row keyed by a unique ISO 639-3 code paired with a language name. Only two of the eight columns (iso_639_3, name) parsed cleanly as text; the other six — including data_sources, glottolog, speaker_count, and us_indigenous — were skipped as nested or non-scalar structures and will need flattening before they yield insight. The name column is the most interesting surface feature: it averages about 9 characters, is single-word ~73% of the time, and its top tokens reveal heavy use of regional qualifiers like 'southern', 'northern', 'eastern', and 'central', plus 152–153 entries containing 'language' or 'sign'. Start by unpacking the skipped object columns (especially speaker_count and glottolog) and look at name-token frequencies to understand naming conventions and language-family clustering.

This column holds ISO 639-3 language codes: every value is exactly 3 characters, single-word, and unique across all 7130 rows (vocab_size 7130, len_min/max 3, one_word_rate 1.0). With n_unique equal to n and zero nulls or duplicates, it functions as a primary key for languages rather than a feature. Sample tokens like 'aou', 'aiw', 'aas' match the ISO 639-3 three-letter convention.

This column appears to be a unique name identifier, likely for languages given the prominence of 'language', 'sign', 'zapotec', 'mixtec', and 'naga' in top words. All 7130 values are unique (n_unique equals n) with zero nulls or duplicates, and 72.9% are single words with a mean length of ~9 characters. The directional modifiers (southern, northern, western, eastern, central) suggest many entries are regional language variants.

The column "joshua_project" was skipped by the profiler, so no type, cardinality, or value statistics are available beyond a row count of 7130 and a null rate of 0.0. Without unique counts or sample values it is not possible to infer whether this is an identifier, code, or descriptive field. The name suggests a reference to the Joshua Project (an ethnographic/missiological dataset), which would typically indicate a people-group code or link.

The column 'glottolog' was skipped by the profiler and carries no computed statistics beyond a row count of 7130 and a null rate of 0.0. The name suggests Glottolog language identifiers (e.g., codes like 'stan1293'), which would align with the ~7000-language scale of that catalogue, but uniqueness, type, and value distribution are all unknown here. No further signal is available to characterise it.

The column `language_history` was skipped by the profiler, which emitted no type, uniqueness, or value statistics. All 7130 rows are non-null, but with `kind` reported as unknown and `stats` empty, nothing can be inferred about the contents from this evidence alone. The name suggests a record of languages (possibly a list or sequence per row), which would explain why a scalar profiler bailed out.

The column `us_indigenous` was skipped by the profiler, so its data type and value distribution are unknown. We can only confirm it has 7130 rows with a 0.0 null rate; cardinality and any descriptive statistics are missing. Without further inspection it is impossible to tell whether this is a flag, category, or something else.

Column `speaker_count` was skipped by the profiler, so no type, cardinality, or distribution stats are available beyond a row count of 7130 and zero nulls. The name suggests an integer count of speakers per record, but this cannot be confirmed from the evidence. Re-profile with the appropriate parser before drawing conclusions.

The column 'data_sources' was skipped by saturn's profiler (alerts: 'skipped') and reports kind 'unknown' with no unique count or stats. Only the row count (7130) and a null_rate of 0.0 are available, so the actual content and structure are unverified here. Likely a nested or non-scalar field (e.g. list/struct of source identifiers) that the profiler could not flatten.