Triple
T420285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port of Seattle |
E8086
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special-purpose district |
C2259
|
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: special-purpose district Context triple: [Port of Seattle, instanceOf, special-purpose district]
-
A.
special court
A special court is a judicial body established to handle specific types of cases or issues outside the jurisdiction or procedures of ordinary courts, often with specialized rules, judges, or limited subject matter.
-
B.
public school district
A public school district is a government-funded administrative entity responsible for managing and operating a group of public schools within a defined geographic area.
-
C.
census-designated place
A census-designated place is a concentration of population identified by the United States Census Bureau for statistical purposes, lacking separate municipal government but resembling an incorporated place in terms of settlement and community identity.
-
D.
mixed-use development district
A mixed-use development district is a designated urban area that intentionally combines residential, commercial, recreational, and sometimes industrial uses within a walkable, integrated environment to promote vibrant, efficient, and sustainable community life.
-
E.
academic district
An academic district is a designated area within a city or region where educational institutions and related facilities are concentrated, fostering learning, research, and scholarly activities.
- F. None of above. chosen
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_69a2e7f1d1bc81909cf2dc9754a3c334 |
completed | Feb. 28, 2026, 1:04 p.m. |
Created at: Feb. 28, 2026, 1:11 p.m.