Triple
T36991723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | downtown Seattle and University of Washington |
E915120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | pair of urban districts |
C13973
|
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: pair of urban districts Context triple: [downtown Seattle and University of Washington, instanceOf, pair of urban districts]
-
A.
pair of cities
chosen
A pair of cities is a conceptual grouping of two distinct urban locations considered together for comparison, connection, or joint analysis.
-
B.
dual city urban core
A dual city urban core is a central metropolitan area characterized by two closely linked yet distinct hubs—often differing in function, density, or socio-economic profile—that together form the primary engine of a region’s economic, cultural, and infrastructural activity.
-
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.
group of central business districts
A group of central business districts is a collection of geographically distinct urban cores where commercial, financial, and administrative activities are highly concentrated and functionally interconnected.
-
E.
urban ensemble
An urban ensemble is a cohesive grouping of buildings, public spaces, and infrastructure whose combined form, function, and character create a distinct, perceivable urban identity.
- 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_69f76e8f1a8c81909db172ed31304971 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.