WEBVTT 00:00:00.000 --> 00:00:03.879 OK, so imagine you're on a road trip. Oh, I love 00:00:03.879 --> 00:00:06.459 a good road trip. Yeah. Driving through the sweeping, 00:00:06.919 --> 00:00:09.679 sun -baked landscapes of New Mexico. Beautiful 00:00:09.679 --> 00:00:11.720 out there. It really is. You've got your hiking 00:00:11.720 --> 00:00:13.880 boots in the trunk, windows are down, your favorite 00:00:13.880 --> 00:00:17.079 playlist is going, and you grab your phone to 00:00:17.079 --> 00:00:19.600 type your destination into the map. Right. You 00:00:19.600 --> 00:00:23.899 type in San Mateo Mountains and, you know, the 00:00:23.899 --> 00:00:26.280 voice on your device chimes back, calculating 00:00:26.280 --> 00:00:28.780 route. Just like it always does. Exactly. You 00:00:28.780 --> 00:00:32.479 put the car in drive. But here is the massive 00:00:32.479 --> 00:00:35.380 hidden catch with this specific search. Oh, boy. 00:00:35.960 --> 00:00:38.200 When you hit that Go button, you actually only 00:00:38.200 --> 00:00:40.619 have a 25 % chance of heading to the right place. 00:00:40.939 --> 00:00:44.359 Wait, really? Just 25 %? Yeah. Because out there 00:00:44.359 --> 00:00:46.880 in the high desert, there are four completely 00:00:46.880 --> 00:00:50.380 distinct geographical locations claiming variations 00:00:50.380 --> 00:00:54.460 of that exact same name. It's basically the ultimate 00:00:54.460 --> 00:00:57.479 cartographical shell game. Totally. Because, 00:00:57.659 --> 00:00:59.619 I mean, we're so conditioned to rely on our digital 00:00:59.619 --> 00:01:01.799 maps and encyclopedias, right? We expect them 00:01:01.799 --> 00:01:04.859 to give us absolute pinpoint certainty. We really 00:01:04.859 --> 00:01:07.159 do. We just trust the machine. Right. We expect 00:01:07.159 --> 00:01:10.159 a search bar to be this like Oracle that knows 00:01:10.159 --> 00:01:13.560 our exact intent. But in this specific case, 00:01:14.140 --> 00:01:16.159 the architecture of the map essentially throws 00:01:16.159 --> 00:01:18.579 its hands up. It just gives up. Pretty much. 00:01:18.659 --> 00:01:20.540 It hits the brakes and asks, you know, wait, 00:01:20.560 --> 00:01:22.500 which one did you actually mean? OK, let's unpack 00:01:22.500 --> 00:01:25.400 this because today's deep dive is centered entirely 00:01:25.400 --> 00:01:29.180 around a single, astonishingly brief Wikipedia 00:01:29.180 --> 00:01:32.060 disambiguation page. Yes, the entry for the San 00:01:32.060 --> 00:01:34.980 Mateo Mountains. Right. And our mission today 00:01:34.980 --> 00:01:38.540 is to untangle this surprisingly dense web of 00:01:38.540 --> 00:01:41.560 identical geographical names in New Mexico. We 00:01:41.560 --> 00:01:43.459 want to make sure that if you, the listener, 00:01:43.700 --> 00:01:46.319 are ever trying to track down this elusive location, 00:01:46.579 --> 00:01:49.510 you never get lost. That's a noble goal. I try, 00:01:50.030 --> 00:01:51.969 because discovering this page isn't just about, 00:01:51.969 --> 00:01:54.349 you know, avoiding a wrong turn on a hike. No, 00:01:54.349 --> 00:01:56.390 far from it. I mean, this short document serves 00:01:56.390 --> 00:01:59.469 as a perfect microscopic case study. A case study 00:01:59.469 --> 00:02:01.909 in what, exactly? In how human history and digital 00:02:01.909 --> 00:02:05.129 information overlap and how they often clash. 00:02:05.510 --> 00:02:07.730 Clash is a good word for it. Yeah, it reveals 00:02:07.730 --> 00:02:11.250 how easily even the most vast, sophisticated 00:02:11.250 --> 00:02:14.569 encyclopedias are forced to build these dedicated 00:02:14.569 --> 00:02:16.969 disambiguation safety nets. Just to keep the 00:02:16.969 --> 00:02:18.810 whole thing from falling apart. Basically, yeah, 00:02:18.990 --> 00:02:21.310 just to keep the underlying database from collapsing. 00:02:21.889 --> 00:02:24.030 It's a brilliant illustration of the friction 00:02:24.030 --> 00:02:28.050 between organic, messy human naming habits and 00:02:28.050 --> 00:02:30.610 the rigid needs of modern digital architecture. 00:02:31.150 --> 00:02:33.490 So let's actually look at the literal text of 00:02:33.490 --> 00:02:35.930 this source, because this page, this specific 00:02:35.930 --> 00:02:38.729 Wikipedia entry, it isn't an article about a 00:02:38.729 --> 00:02:40.789 mountain. Right. There's no topography discussed 00:02:40.789 --> 00:02:44.250 here. None at all. It exists solely to fix navigational 00:02:44.250 --> 00:02:47.210 errors. It's like a digital traffic cop. I like 00:02:47.210 --> 00:02:49.550 that analogy. And the very first thing it says 00:02:49.550 --> 00:02:52.449 is this incredibly polite, almost defeated warning. 00:02:52.569 --> 00:02:55.129 What does it say? It says, if an internal link 00:02:55.129 --> 00:02:57.830 incorrectly led you here, you may wish to change 00:02:57.830 --> 00:03:00.930 the link to point directly to the intended article. 00:03:01.150 --> 00:03:04.090 Wow. Right. It is basically the internet apologizing 00:03:04.090 --> 00:03:06.250 for being thoroughly confused. That's amazing. 00:03:06.889 --> 00:03:09.349 And right below that warning, it presents us 00:03:09.349 --> 00:03:11.830 with our very first location, which is the San 00:03:11.830 --> 00:03:14.169 Mateo Mountains situated in Socorro County, New 00:03:14.169 --> 00:03:16.689 Mexico. So what's really fascinating here is 00:03:16.689 --> 00:03:20.409 how that single sentence exposes a fundamental 00:03:20.409 --> 00:03:23.370 vulnerability in how we organize knowledge today. 00:03:23.750 --> 00:03:25.889 How so? Well, this is what computer scientists 00:03:25.889 --> 00:03:29.229 might call an ontological mapping problem. Ontological 00:03:29.229 --> 00:03:31.870 mapping problem, okay. Fancy term. Right, but 00:03:31.870 --> 00:03:34.490 I mean, a system like Wikipedia is built on the 00:03:34.490 --> 00:03:36.389 assumption of a one -to -one relationship. Like 00:03:36.389 --> 00:03:39.569 one name equals one place. Exactly. A unique 00:03:39.569 --> 00:03:43.060 identifier. like a URL or an internal link connecting 00:03:43.060 --> 00:03:46.199 to a specific concept in the real world. The 00:03:46.199 --> 00:03:49.360 database craves a primary key. It wants neatly 00:03:49.360 --> 00:03:52.110 organized ones and zeros. But the real world 00:03:52.110 --> 00:03:54.509 is definitely not neatly organized ones and zeros. 00:03:54.530 --> 00:03:57.509 Not at all. Human geography is deeply semantic 00:03:57.509 --> 00:04:00.289 and heavily overloaded. It absolutely refuses 00:04:00.289 --> 00:04:02.750 to obey the rules of digital logic. It's just 00:04:02.750 --> 00:04:04.969 too messy. Yeah. So when the system encounters 00:04:04.969 --> 00:04:07.229 four different physical realities sharing the 00:04:07.229 --> 00:04:09.710 identical text string of San Mateo, the automated 00:04:09.710 --> 00:04:12.789 routing just fails. The system panics. It really 00:04:12.789 --> 00:04:15.750 does. It has to generate this traffic cop page 00:04:15.750 --> 00:04:20.410 to force the user to pause, step in and manually 00:04:20.389 --> 00:04:24.470 verify their own intention. It's like having 00:04:24.470 --> 00:04:26.889 four people named John Smith at the same party. 00:04:27.129 --> 00:04:28.930 Oh, that's a great way to put it. But it's worse. 00:04:29.009 --> 00:04:31.649 It's like being the bouncer at that party, equipped 00:04:31.649 --> 00:04:34.829 with a digital scanner that's programmed to only 00:04:34.829 --> 00:04:37.730 accept one unique barcode per guest. Right. One 00:04:37.730 --> 00:04:40.649 barcode, one person. Yeah. And suddenly, four 00:04:40.649 --> 00:04:43.009 different guys walk up to the door, all handing 00:04:43.009 --> 00:04:45.589 you the exact same barcode. You can't just scan 00:04:45.589 --> 00:04:47.670 them in. The scanner would just flash in error. 00:04:47.889 --> 00:04:49.709 Exactly. You have to stop the line, pull them 00:04:49.709 --> 00:04:51.810 aside, and start checking their physical driver's 00:04:51.810 --> 00:04:54.939 licenses just to figure out who is who. Like, 00:04:55.079 --> 00:04:57.199 oh, you're the John Smith from Socorro County. 00:04:57.399 --> 00:04:59.060 Right. You have to look at the secondary data. 00:04:59.279 --> 00:05:00.920 But I got to push back on this a little bit. 00:05:00.920 --> 00:05:03.519 Go for it. Because we see search engines handle 00:05:03.519 --> 00:05:06.060 this kind of stuff all the time. Why wouldn't 00:05:06.060 --> 00:05:08.579 an encyclopedia just apply a popularity metric? 00:05:08.680 --> 00:05:11.540 The popularity contest approach. Yeah, like why 00:05:11.540 --> 00:05:13.879 not just pick the biggest mountain range or the 00:05:13.879 --> 00:05:16.959 tallest or the most famous one, crown it as the 00:05:16.959 --> 00:05:20.259 main page, and redirect everyone there? Serious 00:05:20.259 --> 00:05:22.519 question. Wouldn't that be infinitely more efficient 00:05:22.519 --> 00:05:24.980 than forcing everyone into this digital waiting 00:05:24.980 --> 00:05:27.540 room? I mean, it would absolutely be more efficient 00:05:27.540 --> 00:05:31.240 for the server, and frankly, it is a very common 00:05:31.240 --> 00:05:34.800 impulse in system design. We naturally want to 00:05:34.800 --> 00:05:37.759 create a hierarchy of importance to streamline 00:05:37.759 --> 00:05:40.180 the user experience. Right. Make it easy for 00:05:40.180 --> 00:05:42.759 90 % of people. But this raises an important 00:05:42.759 --> 00:05:45.660 question. Who gets to decide which mountain's 00:05:45.660 --> 00:05:48.579 the most important? Oh. Yeah, I see where you're 00:05:48.579 --> 00:05:51.339 going with this. If a centralized encyclopedia 00:05:51.339 --> 00:05:54.339 algorithm... arbitrarily crowns the Socorro County 00:05:54.339 --> 00:05:57.079 Mountains as the main San Mateo Mountains just 00:05:57.079 --> 00:05:59.000 because they get more search traffic? What happens 00:05:59.000 --> 00:06:00.839 to the others? They just get buried. They're 00:06:00.839 --> 00:06:03.220 essentially erasing the local reality for the 00:06:03.220 --> 00:06:05.100 people living near the other three locations. 00:06:05.279 --> 00:06:08.399 So it's about fairness. Exactly. A disambiguation 00:06:08.399 --> 00:06:11.379 page isn't just a technical fix. It's an exercise 00:06:11.379 --> 00:06:15.040 in strict epistemological neutrality. Epistemological 00:06:15.040 --> 00:06:17.620 neutrality, meaning it doesn't take sides. Right. 00:06:17.790 --> 00:06:21.250 It refuses to impose an external hierarchy on 00:06:21.250 --> 00:06:24.389 a flat geographic reality. It admits that all 00:06:24.389 --> 00:06:27.230 of these locations have an equal valid claim 00:06:27.230 --> 00:06:30.430 to the name and it leaves a final choice entirely 00:06:30.430 --> 00:06:33.199 up to the user. OK, so it's a philosophical choice 00:06:33.199 --> 00:06:36.779 disguised as a software feature. It refuses to 00:06:36.779 --> 00:06:38.639 play favorites. That's a perfect way to summarize 00:06:38.639 --> 00:06:41.139 it. All right. So Socorro County gets the first 00:06:41.139 --> 00:06:43.319 slot on the list, neatly contained within its 00:06:43.319 --> 00:06:46.160 borders. But here's where it gets really interesting. 00:06:46.220 --> 00:06:49.100 Oh, it gets worse. Way worse. Because the source 00:06:49.100 --> 00:06:51.910 introduces us. to the second location. And this 00:06:51.910 --> 00:06:53.689 is where the cartography starts to get a little 00:06:53.689 --> 00:06:56.410 aggressive. Aggressive how? Well, the text lists 00:06:56.410 --> 00:06:59.449 another distinct range called the San Mateo Mountains. 00:06:59.750 --> 00:07:02.069 But this one is located in Cibola and McKinley 00:07:02.069 --> 00:07:04.430 counties. OK, two counties. Yeah. And crucially, 00:07:04.910 --> 00:07:07.610 the source explicitly notes that this specific 00:07:07.610 --> 00:07:11.389 range includes Mount Taylor. They literally have 00:07:11.389 --> 00:07:14.629 to drag a sub feature, like a specific peak into 00:07:14.629 --> 00:07:17.430 the description just to act as an anchor. Right. 00:07:17.430 --> 00:07:19.370 To help tell these mountains apart from the first 00:07:19.370 --> 00:07:21.610 ones. Exactly. It's like you're saying, no, no, 00:07:21.629 --> 00:07:23.490 we're the San Mateo Mountains with Mount Taylor. 00:07:23.670 --> 00:07:26.930 Precisely. Because the primary identifier, the 00:07:26.930 --> 00:07:30.269 name San Mateo Mountains, has completely failed 00:07:30.269 --> 00:07:33.139 as a unique. query. It's useless now. Right. 00:07:33.180 --> 00:07:35.339 So the database has to zoom in closer to find 00:07:35.339 --> 00:07:37.800 a new variable. It has to pull in Mount Taylor 00:07:37.800 --> 00:07:40.439 to act as a geographical fingerprint. That fingerprint, 00:07:40.560 --> 00:07:42.560 yeah. It's a compensatory mechanism. When the 00:07:42.560 --> 00:07:45.240 broad category fails to differentiate the data, 00:07:45.720 --> 00:07:48.600 the system relies on relational clustering. Meaning 00:07:48.600 --> 00:07:50.899 it pairs things together? Exactly. It essentially 00:07:50.899 --> 00:07:53.920 says, OK, San Mateo is useless to us right now, 00:07:54.160 --> 00:07:56.699 so look for the node that contains San Mateo 00:07:56.699 --> 00:07:59.800 and the Mount Taylor. It uses specific details 00:07:59.800 --> 00:08:01.980 to create the distinction that the name alone 00:08:01.980 --> 00:08:04.199 can't provide. Well, let's look at the physical 00:08:04.199 --> 00:08:06.980 realities of the map here. The first mountain 00:08:06.980 --> 00:08:10.079 range sits squarely inside Socorro County. It's 00:08:10.079 --> 00:08:12.860 geographically tidy. Very tidy. But the second 00:08:12.860 --> 00:08:15.959 range physically crosses the borders of two completely 00:08:15.959 --> 00:08:19.220 different counties, Cibola and McKinley. Does 00:08:19.220 --> 00:08:22.040 the fact that this mountain range sprawls across 00:08:22.040 --> 00:08:24.720 two different county lines make it even harder 00:08:24.720 --> 00:08:27.839 to map and classify? Because from a logistical 00:08:27.839 --> 00:08:30.379 standpoint, it feels like it's actively defying 00:08:30.379 --> 00:08:32.759 containment. Oh, without a doubt. If we connect 00:08:32.759 --> 00:08:35.039 this to the bigger picture, you are looking at 00:08:35.039 --> 00:08:38.480 the ultimate friction between organic earth and 00:08:38.480 --> 00:08:41.519 rigid human grids. Organic earth versus human 00:08:41.519 --> 00:08:43.740 grids. grids yeah because geographical borders 00:08:43.740 --> 00:08:46.639 like county lines they're entirely human inventions 00:08:46.639 --> 00:08:49.659 it's just made up exactly they are invisible 00:08:49.659 --> 00:08:52.500 arbitrary geometric lines drawn on a piece of 00:08:52.500 --> 00:08:56.259 paper by a surveyor usually for like taxes or 00:08:56.259 --> 00:08:58.720 something. Right, political tax or administrative 00:08:58.720 --> 00:09:01.840 reasons. But geological features, like a massive 00:09:01.840 --> 00:09:04.039 mountain range, they operate on a time scale 00:09:04.039 --> 00:09:06.100 of millions of years. They don't care about our 00:09:06.100 --> 00:09:08.419 paperwork. They really don't. They are the result 00:09:08.419 --> 00:09:11.100 of tectonic plates violently pushing rock up 00:09:11.100 --> 00:09:13.440 from the Earth's crust. They do not care about 00:09:13.440 --> 00:09:15.639 our invisible surveyor lines. They just erupt 00:09:15.639 --> 00:09:18.980 wherever the physics dictate. Exactly. So when 00:09:18.980 --> 00:09:21.340 you have a mountain range crossing from Cibola 00:09:21.340 --> 00:09:23.960 into McKinley County, you suddenly have an object 00:09:23.960 --> 00:09:27.580 that exists in two mutually exclusive administrative 00:09:27.580 --> 00:09:30.200 containers. Which means double the bureaucracy. 00:09:30.460 --> 00:09:32.820 Oh, absolutely. You have two different local 00:09:32.820 --> 00:09:35.220 governments, two different zoning boards, and 00:09:35.220 --> 00:09:37.340 two different sets of emergency services that 00:09:37.340 --> 00:09:39.980 have to deal with it. What a nightmare. It radically 00:09:39.980 --> 00:09:42.539 compounds the need for high level disambiguation. 00:09:42.730 --> 00:09:45.649 because the location cannot simply be pigeonholed 00:09:45.649 --> 00:09:48.690 into a single database cell. It just defies the 00:09:48.690 --> 00:09:51.110 tidy columns of a spreadsheet. So you have a 00:09:51.110 --> 00:09:53.230 bureaucratic headache layered right on top of 00:09:53.230 --> 00:09:55.870 a geological one. You have mountains ignoring 00:09:55.870 --> 00:09:58.730 the county lines and encyclopedias scrambling 00:09:58.730 --> 00:10:01.190 to build subcategories just to explain it all. 00:10:01.250 --> 00:10:03.610 That's the reality of it. Which transitions us 00:10:03.610 --> 00:10:06.309 perfectly to our third location because we just 00:10:06.309 --> 00:10:08.590 saw how a massive mountain range causes administrative 00:10:08.590 --> 00:10:10.750 chaos by spilling into McKinley County. Right. 00:10:10.990 --> 00:10:13.549 But human naming habits make this even worse 00:10:13.549 --> 00:10:16.950 because entirely contained within that very same 00:10:16.950 --> 00:10:19.669 county sits a completely different geological 00:10:19.720 --> 00:10:22.000 feature claiming the exact same name. Oh, this 00:10:22.000 --> 00:10:24.860 is my favorite part. It's so wild. The source 00:10:24.860 --> 00:10:29.500 introduces us to the San Mateo Mesa and its location, 00:10:30.159 --> 00:10:33.379 McKinley County, New Mexico. The very same McKinley 00:10:33.379 --> 00:10:36.139 County that contains the northern half of the 00:10:36.139 --> 00:10:39.320 Second Mountain Range. Yes. It is a localized 00:10:39.320 --> 00:10:42.879 naming traffic jam of epic proportions. It really 00:10:42.879 --> 00:10:45.460 is. This is like having a main street and a main 00:10:45.460 --> 00:10:48.139 boulevard intersecting in the exact same small 00:10:48.139 --> 00:10:50.899 town. It's so confusing for everyone. If a traveler 00:10:50.899 --> 00:10:53.320 is driving through McKinley County, New Mexico, 00:10:53.320 --> 00:10:56.580 and they ask a local for directions to San Mateo, 00:10:56.639 --> 00:10:58.519 how in the world are they supposed to know if 00:10:58.519 --> 00:11:00.340 they're heading toward the towering mountain 00:11:00.340 --> 00:11:03.019 range or the flat mesa? They have no idea. Feels 00:11:03.019 --> 00:11:05.799 like a recipe for absolute chaos. It does. And 00:11:05.799 --> 00:11:08.139 this is where the specific geological terminology 00:11:08.139 --> 00:11:10.759 becomes the absolute last line of defense. the 00:11:10.759 --> 00:11:12.980 database. You mean the words mountain versus 00:11:12.980 --> 00:11:15.740 mesa. Exactly because a mountain is typically 00:11:15.740 --> 00:11:18.799 characterized by a prominent elevated peak. It 00:11:18.799 --> 00:11:21.580 has a sharp verticality. Pointy at the top. Right. 00:11:21.899 --> 00:11:24.259 A mesa on the other hand is an isolated flat 00:11:24.259 --> 00:11:26.960 -topped elevation with steep sides. I mean the 00:11:26.960 --> 00:11:29.500 word literally translates to table in Spanish. 00:11:29.720 --> 00:11:33.779 So it's flat. Very flat. So the only way to differentiate 00:11:33.779 --> 00:11:36.360 these two locations within the exact same county 00:11:36.360 --> 00:11:39.940 is to rely entirely on the precise physical shape 00:11:39.940 --> 00:11:43.480 of the rock formation. The nouns mountain and 00:11:43.480 --> 00:11:45.799 mesa are doing an incredible amount of heavy 00:11:45.799 --> 00:11:47.980 lifting here. If you drop those descriptive words 00:11:47.980 --> 00:11:51.340 and just say I'm going to San Mateo, the navigational 00:11:51.340 --> 00:11:54.259 system collapses entirely. You are stranded in 00:11:54.259 --> 00:11:56.759 the desert. pretty much. But we really have to 00:11:56.759 --> 00:11:59.159 pause and look at the psychology of this. It's 00:11:59.159 --> 00:12:01.860 wild that the early residents of McKinley County 00:12:01.860 --> 00:12:04.019 allowed this to happen. It is a bit baffling. 00:12:04.200 --> 00:12:07.580 You have pioneers or settlers who look at a giant 00:12:07.580 --> 00:12:09.860 mountain range that crosses into their territory 00:12:09.860 --> 00:12:12.620 and they say Yes, that's San Mateo. OK, makes 00:12:12.620 --> 00:12:14.799 sense. And then presumably, some of those same 00:12:14.799 --> 00:12:17.679 people look at a giant flat -topped rock sitting 00:12:17.679 --> 00:12:19.799 entirely inside their territory and say, you 00:12:19.799 --> 00:12:21.799 know what, let's call that San Mateo too. Right. 00:12:21.940 --> 00:12:24.299 Why does this happen? Is it just the staggering 00:12:24.299 --> 00:12:27.399 lack of creativity? Well, it might look like 00:12:27.399 --> 00:12:29.940 a lack of creativity to us now, sitting in front 00:12:29.940 --> 00:12:32.820 of a global map. But it actually speaks volumes 00:12:32.820 --> 00:12:35.360 about how place names actually originate. Ah, 00:12:35.360 --> 00:12:38.129 so. It is the fundamental difference between 00:12:38.129 --> 00:12:40.789 the local perspective and the bird's eye view. 00:12:40.950 --> 00:12:43.230 OK, I'm following. When early communities were 00:12:43.230 --> 00:12:45.909 naming landmarks, they were doing it based on 00:12:45.909 --> 00:12:49.669 immediate local utility, not future proofing 00:12:49.669 --> 00:12:51.769 for a digital database. They weren't thinking 00:12:51.769 --> 00:12:55.149 about Wikipedia. Not at all. They weren't thinking 00:12:55.149 --> 00:12:58.149 about how a Silicon Valley programmer might one 00:12:58.149 --> 00:13:02.360 day try to index their landscape. Often, a prominent 00:13:02.360 --> 00:13:04.539 feature was named after a patron saint. Like 00:13:04.539 --> 00:13:07.019 Saint Matthew. Right, Saint Matthew or San Mateo. 00:13:07.539 --> 00:13:09.700 Perhaps because it was discovered on that saint's 00:13:09.700 --> 00:13:12.379 feast day, or because the local mission was dedicated 00:13:12.379 --> 00:13:14.480 to him. So they were just looking at the world 00:13:14.480 --> 00:13:16.960 from their own front porch. Precisely. Yeah. 00:13:17.240 --> 00:13:19.399 They named what was relevant to them on that 00:13:19.399 --> 00:13:22.139 specific day. They didn't have the capacity or 00:13:22.139 --> 00:13:25.720 the need really to check if a community 20 miles 00:13:25.720 --> 00:13:28.440 over the ridge had done the exact same thing 00:13:28.440 --> 00:13:30.440 with a different rock formation. Because it didn't 00:13:30.440 --> 00:13:33.700 affect them. Exactly. It's only centuries later 00:13:33.700 --> 00:13:36.740 when we try to aggregate all of this highly localized 00:13:36.740 --> 00:13:40.179 organic information into a single centralized 00:13:40.179 --> 00:13:43.799 database like Wikipedia that these innocent local 00:13:43.799 --> 00:13:46.700 overlaps suddenly turn into massive systemic 00:13:46.700 --> 00:13:49.120 points of confusion. The system is trying to 00:13:49.120 --> 00:13:52.139 force a rigid structure onto a very fluid human 00:13:52.139 --> 00:13:54.620 history. That's exactly it. That is such a profound 00:13:54.620 --> 00:13:56.700 way to look at it. The map is just a collision 00:13:56.700 --> 00:13:59.340 of two completely different eras of human thought. 00:13:59.470 --> 00:14:01.429 It really is a collision. Now we have one more 00:14:01.429 --> 00:14:03.389 location to cover from our source, and this one 00:14:03.389 --> 00:14:05.289 involves looking for a way out of this trap. 00:14:05.769 --> 00:14:08.450 The escape route. We are moving away from current 00:14:08.450 --> 00:14:12.009 geographical overlaps to a historical resolution, 00:14:12.330 --> 00:14:14.929 because according to the text, one of these locations 00:14:14.929 --> 00:14:17.970 actually managed to escape this ontological nightmare 00:14:17.970 --> 00:14:21.549 entirely. Good for them. Right. The fourth entry 00:14:21.549 --> 00:14:23.929 on the page is for the Cerillos Hills, which 00:14:23.929 --> 00:14:26.769 the text associates with Cerillos Hills State 00:14:26.769 --> 00:14:29.799 Park. But the critical detail here is that these 00:14:29.799 --> 00:14:32.139 hills were formerly known as the Sierra de San 00:14:32.139 --> 00:14:35.080 Mateo. Now, if we connect this to the evolution 00:14:35.080 --> 00:14:37.399 of language and identity, this is perhaps the 00:14:37.399 --> 00:14:39.820 most fascinating entry on the page. I agree. 00:14:40.320 --> 00:14:43.279 Sierra is the Spanish word for a mountain range, 00:14:43.940 --> 00:14:46.899 specifically one with a jagged sawtoothed profile. 00:14:47.179 --> 00:14:50.240 Like a saw, yeah. Right. So historically, this 00:14:50.240 --> 00:14:52.960 fourth location shared the exact same root name 00:14:52.960 --> 00:14:55.360 as the others. just in its Spanish variation, 00:14:55.899 --> 00:14:57.899 the Sierra de San Mateo. So it was caught in 00:14:57.899 --> 00:15:01.379 the exact same disambiguation trap. It was. But 00:15:01.379 --> 00:15:04.559 over time, the name evolved. The landscape was 00:15:04.559 --> 00:15:07.059 rebranded to the Sirios Hills. They just changed 00:15:07.059 --> 00:15:09.659 it. Yeah. By completely shedding the San Mateo 00:15:09.659 --> 00:15:13.220 namesake, this specific geological feature effectively 00:15:13.220 --> 00:15:16.460 achieved semantic escape velocity. Semantic escape 00:15:16.460 --> 00:15:19.120 velocity. I love that. It just opted out of the 00:15:19.120 --> 00:15:21.419 database collision entirely. So what does this 00:15:21.419 --> 00:15:23.460 all mean? It means the Cerritos Hills pulled 00:15:23.460 --> 00:15:25.639 off the geographical equivalent of a massive 00:15:25.639 --> 00:15:28.659 corporate restructuring just to escape a trademark 00:15:28.659 --> 00:15:30.740 lawsuit. That's a very modern way to look at 00:15:30.740 --> 00:15:33.279 it. But yeah, they saw the chaos happening in 00:15:33.279 --> 00:15:36.500 Socorro, Cibola and McKinley counties. Everyone 00:15:36.500 --> 00:15:38.580 fighting over the right to use the San Mateo 00:15:38.580 --> 00:15:40.080 primary key. And they just threw their hands 00:15:40.080 --> 00:15:42.220 up and said, we're out. We are the Cerritos Hills 00:15:42.220 --> 00:15:45.440 now. They found a loophole. They completely rebranded, 00:15:45.460 --> 00:15:47.919 they got their own State Park identity, they 00:15:47.919 --> 00:15:49.879 stepped completely out of the shadow of the other 00:15:49.879 --> 00:15:53.320 San Mateers, and most importantly, they finally 00:15:53.320 --> 00:15:56.379 got a clean, dedicated Wikipedia page all to 00:15:56.379 --> 00:15:59.039 themselves. That's the real prize. Honestly, 00:15:59.240 --> 00:16:02.120 it is a brilliant strategy. It is a highly pragmatic 00:16:02.120 --> 00:16:05.799 solution to a deeply complex information problem. 00:16:06.559 --> 00:16:09.360 I mean... When disambiguation fails, when the 00:16:09.360 --> 00:16:11.480 geographical overlap becomes too dense for the 00:16:11.480 --> 00:16:13.980 system to gracefully manage, sometimes the only 00:16:13.980 --> 00:16:16.539 viable way out is a complete renaming. Start 00:16:16.539 --> 00:16:19.279 fresh. Right. It serves as a powerful reminder 00:16:19.279 --> 00:16:22.039 that the map is never a finished product. It's 00:16:22.039 --> 00:16:24.600 a living, breathing document that constantly 00:16:24.600 --> 00:16:27.759 shifts and adapts as human needs, migrations, 00:16:27.879 --> 00:16:30.200 and frustrations change. That makes total sense. 00:16:30.419 --> 00:16:32.340 The Surrealist Hills adapting their name is a 00:16:32.340 --> 00:16:34.360 perfect example of human intervention solving 00:16:34.360 --> 00:16:37.039 a cartographical crisis that a database alone 00:16:37.039 --> 00:16:39.259 could never resolve. It really is. It's like 00:16:39.259 --> 00:16:41.899 they successfully legally change their name just 00:16:41.899 --> 00:16:44.039 to get off a digital watch list. Basically, yeah. 00:16:44.519 --> 00:16:46.519 All right. Well, let's take a breath and do a 00:16:46.519 --> 00:16:49.480 quick satisfying recap of the journey we've just 00:16:49.480 --> 00:16:52.330 been on. Let's do it. We started by looking at 00:16:52.330 --> 00:16:55.289 a single, incredibly brief disambiguation page, 00:16:55.409 --> 00:16:58.889 and we ended up navigating a surprisingly dense, 00:16:59.049 --> 00:17:02.250 complex slice of New Mexico geography and database 00:17:02.250 --> 00:17:04.150 architecture. We covered a lot of ground. We 00:17:04.150 --> 00:17:06.930 really did. We have the San Mateo Mountains sitting 00:17:06.930 --> 00:17:09.990 neatly and obediently in Secora County. We have 00:17:09.990 --> 00:17:13.029 the rebellious San Mateo Mountains defying administrative 00:17:13.029 --> 00:17:15.789 logic by crossing the borders of Cibola and McKinley 00:17:15.789 --> 00:17:19.269 counties, relying on Mount Taylor as their identifying 00:17:19.269 --> 00:17:21.750 anchor. Right, the trouble. makers. Then we have 00:17:21.750 --> 00:17:24.589 the San Mateo Mesa creating a massive local headache 00:17:24.589 --> 00:17:27.170 right in the middle of McKinley County relying 00:17:27.170 --> 00:17:30.150 purely on its flat top shape to stand out. The 00:17:30.150 --> 00:17:32.990 table. Exactly. And finally we have the formerly 00:17:32.990 --> 00:17:36.410 named Sierra de San Mateo which brilliantly rebranded 00:17:36.410 --> 00:17:39.190 itself into the Cerillos Hills State Park to 00:17:39.190 --> 00:17:42.029 escape the madness altogether. It really is a 00:17:42.029 --> 00:17:45.079 remarkable amount of geographical complexity, 00:17:45.599 --> 00:17:48.460 historical psychology, and computer science distilled 00:17:48.460 --> 00:17:51.579 into a tiny handful of bullet points. It's so 00:17:51.579 --> 00:17:54.579 dense. It truly highlights how much silent heavy 00:17:54.579 --> 00:17:58.400 lifting of simple disambiguation page is doing 00:17:58.400 --> 00:18:01.259 behind the scenes every single day. I mean, it 00:18:01.259 --> 00:18:03.819 is the only thing keeping the chaos organized. 00:18:03.960 --> 00:18:06.259 It really is. But before we wrap up this deep 00:18:06.259 --> 00:18:09.859 dive, there is one final, almost haunting detail 00:18:09.859 --> 00:18:12.059 hiding at the very bottom of our source text. 00:18:12.599 --> 00:18:14.920 What's that? In the fine print, the footer of 00:18:14.920 --> 00:18:16.799 the page notes that this disambiguation page 00:18:16.799 --> 00:18:20.740 was last edited on September 11, 2011. Oh, wow. 00:18:21.160 --> 00:18:23.740 Yeah, let that sink in for a second. That page 00:18:23.740 --> 00:18:26.819 has sat untouched, frozen in digital amber for 00:18:26.819 --> 00:18:29.039 well over a decade. It is wild. I mean, in the 00:18:29.039 --> 00:18:30.779 context of the internet, where millions of edits 00:18:30.779 --> 00:18:33.079 happen daily, a decade is a staggering amount 00:18:33.079 --> 00:18:35.420 of time. It's an eternity. It implies a kind 00:18:35.420 --> 00:18:38.539 of finalized stasis, as if the map of this specific 00:18:38.539 --> 00:18:40.660 area has been permanently settled. But here's 00:18:40.660 --> 00:18:42.319 the provocative thought I want to leave you with. 00:18:42.319 --> 00:18:45.039 I'm ready. If that page has been serving as the 00:18:45.039 --> 00:18:47.819 ultimate digital traffic cop for over a decade 00:18:47.819 --> 00:18:50.980 without a single update, how many lost travelers 00:18:50.980 --> 00:18:53.119 have stumbled into the wrong New Mexico County 00:18:53.119 --> 00:18:55.359 since then? Probably more than a few. Right. 00:18:55.680 --> 00:18:58.420 How many people typed San Mateo into their phones, 00:18:59.019 --> 00:19:01.210 clicked the wrong link? and ended up staring 00:19:01.210 --> 00:19:03.890 at a flat mesa instead of the towering mountain 00:19:03.890 --> 00:19:06.990 peak they wanted. It happens. And even more tantalizing, 00:19:07.029 --> 00:19:09.690 it makes you wonder if, out there in the vast, 00:19:10.049 --> 00:19:12.130 expanding developments of the New Mexico desert, 00:19:12.609 --> 00:19:15.710 any new geological features, subdivisions, or 00:19:15.710 --> 00:19:19.170 parks have quietly been dubbed San Mateo in the 00:19:19.170 --> 00:19:21.549 years since 2011. Oh, almost certainly. Features 00:19:21.549 --> 00:19:24.029 that are just sitting out there, completely unlisted, 00:19:24.250 --> 00:19:26.369 just waiting to make the map even more complicated. 00:19:26.549 --> 00:19:28.789 Adding to the chaos. Exactly. So the next time 00:19:28.789 --> 00:19:31.460 you type a desti - into your map, hit go and 00:19:31.460 --> 00:19:33.940 hear that voice say calculating route, just remember 00:19:33.940 --> 00:19:36.980 you might only have a 25 % chance of ending up 00:19:36.980 --> 00:19:37.819 where you think you're going.