Triple
T13060613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | U.S. Census Bureau regions and divisions |
E329186
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographic classification system |
C3353
|
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: geographic classification system Context triple: [U.S. Census Bureau regions and divisions, instanceOf, geographic classification system]
-
A.
geographical region
A geographical region is a defined area of the Earth's surface characterized by shared physical, cultural, political, or environmental features that distinguish it from surrounding areas.
-
B.
geographical concept
A geographical concept is an abstract idea or principle used to understand, describe, and analyze the spatial characteristics, relationships, and processes of the Earth's physical and human environments.
-
C.
geographic code
chosen
A geographic code is a standardized alphanumeric identifier used to represent specific geographic areas or locations for purposes such as mapping, analysis, and data organization.
-
D.
Köppen climate classification
The Köppen climate classification is a widely used system that categorizes the world's climates based on average temperature and precipitation patterns, grouping regions into distinct climate types such as tropical, arid, temperate, continental, and polar.
-
E.
public land classification
Public land classification is the systematic categorization of government-owned lands based on their designated uses, protections, and management objectives, such as conservation, recreation, resource extraction, or development.
- 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_69d80771749c81909a6d9197b9504872 |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 8:59 p.m.