Triple
T14997464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Cienega Mud Springs |
E373994
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical geographic name |
C4613
|
CONCEPT FINISHED |
How this triple was built (1 step)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: historical geographic name Context triple: [La Cienega Mud Springs, instanceOf, historical geographic name]
-
A.
historical place name
chosen
A historical place name is a designation for a geographic location that reflects its identity, usage, or significance during a specific past period, which may differ from its modern name or boundaries.
-
B.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
C.
geographical names authority
A geographical names authority is an entity or system responsible for standardizing, maintaining, and providing authoritative information on the official names and spellings of geographic places.
-
D.
toponymic name
A toponymic name is a personal or family name derived from a geographic place or feature, such as a town, region, or landscape element.
-
E.
historical ethnonym
A historical ethnonym is a name or label historically used to designate a particular ethnic group, people, or population, often reflecting past cultural, political, or linguistic contexts that may differ from present-day usage.
- F. None of above.
Provenance (1 batch)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 2:54 a.m.