Triple
T34508413
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kentucky statistical areas |
E885950
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | United States Census Bureau statistical area grouping |
C17801
|
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: United States Census Bureau statistical area grouping Context triple: [Kentucky statistical areas, instanceOf, United States Census Bureau statistical area grouping]
-
A.
United States micropolitan statistical area grouping
A United States micropolitan statistical area grouping is a collection of adjacent micropolitan statistical areas that are socially and economically linked, typically through commuting patterns and shared regional characteristics.
-
B.
U.S. federal statistical area
A U.S. federal statistical area is a geographic region defined by the federal government, typically based on population density and economic ties, used for collecting, analyzing, and publishing statistical data.
-
C.
statistical geographic areas
Statistical geographic areas are spatially defined regions created for the collection, analysis, and presentation of data about populations, economies, or environments.
-
D.
U.S. Census Bureau-defined area
chosen
A U.S. Census Bureau-defined area is a geographically bounded region delineated by the Census Bureau for the purpose of collecting, analyzing, and publishing standardized demographic and economic data.
-
E.
U.S. Census-defined region
A U.S. Census-defined region is a large, multi-state geographic area established by the U.S. Census Bureau to organize, analyze, and report demographic and economic data.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.