Triple
T25547088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | University District, Seattle |
E640338
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Seattle |
C31568
|
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: district of Seattle Context triple: [University District, Seattle, instanceOf, district of Seattle]
-
A.
region of Seattle
chosen
A region of Seattle represents a specific geographic area within the city, defined by boundaries and associated with particular neighborhoods, landmarks, and administrative or cultural characteristics.
-
B.
city in Washington State
A city in Washington State is an incorporated urban municipality within the state’s boundaries that provides local government services, infrastructure, and regulations to its residents and businesses.
-
C.
neighborhood of Kirkland, Washington
A neighborhood of Kirkland, Washington is a distinct residential and mixed-use area within the city characterized by its local amenities, community identity, and geographic boundaries along Lake Washington’s eastern shore.
-
D.
district of Portland, Oregon
A district of Portland, Oregon is a defined geographic area within the city that groups together neighborhoods sharing common administrative, cultural, or commercial characteristics.
-
E.
county in Washington State
A county in Washington State is an administrative and geographic subdivision of the state that provides local government services, governance, and regional organization for its constituent cities, towns, and unincorporated areas.
- 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_69e75dc101a881909fd33b02174e9768 |
completed | April 21, 2026, 11:21 a.m. |
Created at: April 21, 2026, 3:34 p.m.