Triple
T5288180
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harrisburg–Carlisle metropolitan area |
E119675
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | U.S. metropolitan area |
C61
|
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: U.S. metropolitan area Context triple: [Harrisburg–Carlisle metropolitan area, instanceOf, U.S. metropolitan area]
-
A.
United States micropolitan area
A United States micropolitan area is a geographic region defined by the U.S. Office of Management and Budget centered around an urban core with a population between 10,000 and 49,999, plus adjacent territories with strong social and economic integration.
-
B.
metropolitan area
chosen
A metropolitan area is a densely populated urban region consisting of a central city and its surrounding suburbs and satellite communities, linked by economic, social, and infrastructural ties.
-
C.
Micropolitan Statistical Area
A Micropolitan Statistical Area is a geographic region defined by the U.S. Office of Management and Budget centered around an urban core with a population between 10,000 and 49,999, plus adjacent territories with strong social and economic integration.
-
D.
metropolitan community
A metropolitan community is a densely populated urban area and its surrounding regions where people live, work, and interact within a shared economic, social, and infrastructural network.
-
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_69bd446de5648190b313a90bd96730d2 |
completed | March 20, 2026, 12:58 p.m. |
Created at: March 20, 2026, 1:52 p.m.