Bilateral evidence profiles
Relationship studio
Compare two profiles through their documented relationships and shared records. An indirect connection is not evidence of a direct relationship.
Bilateral query
Build an exact profile-to-profile route
Declared bilateral profile
71213 Zoos and botanic... U.S. Census Bureau
Measurement / 1 hop- Shortest route
- 1declared hop
- Shortest paths
- 1deterministic routes
- Common neighbors
- 2exact intersections
- Packet edges
- 51 cited sources
- Revenue HHI
- 123.1
- Selected-layer neighbors
- 3
- Total neighbors
- 3
- Latest year
- 2022
- Access date
- 2026-07-17
- Selected-layer neighbors
- 1,868
- Total neighbors
- 1,872
- Latest year
- 2026
Supporting edge ledger
Every bridge remains an inspectable declaration
5 exact edges support the shortest paths and common-neighbor intersections in this layer.
Zoos and botanical gardens (NAICS 71213) is classified under Museums, historical sites, and similar institutions (NAICS 7121) in the 2022 NAICS hierarchy.
Zoos and botanical gardens (NAICS 712130) is classified under Zoos and botanical gardens (NAICS 71213) in the 2022 NAICS hierarchy.
2022 Economic Census Concentration of Largest Firms supplies the 2022 employer-firm concentration screen for NAICS 7121.
2022 Economic Census Concentration of Largest Firms supplies the 2022 employer-firm concentration screen for NAICS 71213.
2022 Economic Census Concentration of Largest Firms supplies the 2022 employer-firm concentration screen for NAICS 712130.
Bilateral graph contract
A route is not a finding about its endpoints
Each hop keeps its own evidence label, confidence, source custody, and edge-specific limitation.
A bilateral atlas route preserves a sequence of declared edges for navigation and audit. A direct edge, common neighbor, or multi-hop path does not make the endpoints equivalent, establish ownership or control, assign liability, define an antitrust market, make unlike measures comparable, or show causation.
Reusable bilateral packet
Carry the exact route into analysis
JSON preserves endpoints, shortest paths, common neighbors, nodes, and edge metadata. CSV flattens the complete supporting ledger.