Triple
T26410418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wilmington Metropolitan Division |
E663943
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | metropolitan area subdivision |
C28946
|
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: metropolitan area subdivision Context triple: [Wilmington Metropolitan Division, instanceOf, metropolitan area subdivision]
-
A.
subregion of metropolitan area
chosen
A subregion of a metropolitan area is a geographically or functionally distinct part of a larger urban region, characterized by shared land use, demographics, infrastructure, or economic activity.
-
B.
metropolitan area
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.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
D.
subdivision of district
A subdivision of district is an administrative unit that forms a smaller, constituent part of a larger district within a governmental or organizational hierarchy.
-
E.
sub-metropolitan city
A sub-metropolitan city is an urban administrative unit that is smaller and less populous than a metropolitan city but larger and more developed than a typical municipality, often serving as a regional hub for services, commerce, and governance.
- 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_69ee883931888190901be96d75ee23cc |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 26, 2026, 11:37 p.m.