Person Data
Sorting Rules
phones[],emails[]: current items first, then by confidence (highest first)locations[]: most recently seen first (bylast_seen)socials[]: current items firstexperience[]: current entries first, then by start date (most recent first)education[]: by start date, most recent first- Skills & Languages: alphabetical
- Certifications: by issue date, most recent first
Contact Data Arrays
Phones, Emails, Locations, Socials
Phones and emails place current items first, then higher confidence, so you can rely on the first phone or email being the best available contact method. Locations are ordered by most recently seen (last_seen). Socials place current items first.
Example phone array:
Experience & Education
Experience places current entries first (current: true), followed by past entries by start date (most recent first). You can rely on experience[0] being the current or most recent job. Education is sorted by start date, most recent first.
Skills & Languages
These arrays are sorted alphabetically by thecleaned value:
Certifications
Sorted by issue date, most recent first:Company Data
Sorting Rules
legion_employee_count_by_month[]: chronological (oldest month first)domains[],socials[],tickers[]: no guaranteed ordering
Company
socials[] do not include confidence, num_sources, last_seen, or current fields, so quality-based sorting does not apply. Person socials[] do include these fields and place current items first.Headcount History
Thelegion_employee_count_by_month[] array places the oldest month first:
Why Deterministic Ordering Matters
- Consistency: Same data always appears in the same order
- Predictability: You can rely on
experience[0]being the current job - Filtering: Easier to find primary contact methods
- Testing: Deterministic output makes testing and validation easier
Related Documentation
- Field Formats - Format specifications
- Person Schema Example - See person arrays in context
- Company Schema Example - See company arrays in context