Triple
T6531228
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | United States Census Bureau places in Michigan |
E152234
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | census-designated geographic classification |
C349
|
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: census-designated geographic classification Context triple: [United States Census Bureau places in Michigan, instanceOf, census-designated geographic classification]
-
A.
census-designated place
chosen
A census-designated place is a concentration of population identified by the United States Census Bureau for statistical purposes, lacking separate municipal government but resembling an incorporated place in terms of settlement and community identity.
-
B.
statistical geographic areas
Statistical geographic areas are spatially defined regions created for the collection, analysis, and presentation of data about populations, economies, or environments.
-
C.
census region
A census region is a large geographic area defined by a statistical agency, grouping together multiple states or administrative units for the purpose of organizing, analyzing, and reporting population and economic data.
-
D.
census division
A census division is a geographic area defined by a government statistical agency for the purpose of collecting, organizing, and analyzing population and demographic data.
-
E.
U.S. Census Bureau-defined area
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.
- 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_69c688048ec8819093a47f7d332e12ec |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 1:46 p.m.