Triple
T36991724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | downtown Seattle and University of Washington |
E915120
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | geographic entity grouping |
C29959
|
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: geographic entity grouping Context triple: [downtown Seattle and University of Washington, instanceOf, geographic entity grouping]
-
A.
geographic unit
A geographic unit is a defined spatial area, such as a country, region, or district, used for organizing, analyzing, and managing geographic information and activities.
-
B.
historical geographic entity
A historical geographic entity is a spatially bounded area whose location, extent, or political status has changed or ceased to exist over time, but which is recognized for its past geographic or administrative significance.
-
C.
geographical region pairing
chosen
A geographical region pairing is a conceptual association between two distinct geographic areas, linked for comparison, analysis, or coordinated planning based on shared or contrasting characteristics.
-
D.
geographical region
A geographical region is a defined area of the Earth's surface characterized by shared physical, cultural, political, or environmental features that distinguish it from surrounding areas.
-
E.
geographically based organization
A geographically based organization is an entity whose structure, operations, and membership are primarily defined and organized according to specific physical locations or regions.
- 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.