Triple
T32812732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Central Puget Sound Regional Transit Authority District |
E839200
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | special purpose taxing 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 taxing district Context triple: [Central Puget Sound Regional Transit Authority District, instanceOf, special purpose taxing district]
-
A.
special-purpose district
chosen
A special-purpose district is a limited-purpose local government entity created to perform a specific public function or set of functions—such as water supply, transportation, or education—within a defined geographic area.
-
B.
special-purpose governmental unit
A special-purpose governmental unit is a limited-scope public entity, such as a school district or water authority, created by law to perform a specific governmental function or set of functions within a defined geographic area.
-
C.
special provision
A special provision is a specific clause or condition within a legal or contractual document that creates an exception, modification, or additional requirement to the general rules or terms.
-
D.
special economic zone
A special economic zone is a designated geographic area within a country where business and trade laws differ from the rest of the nation to attract investment, boost exports, and stimulate economic growth.
-
E.
local tax
Local tax is a compulsory financial charge imposed by municipal or regional authorities on individuals, businesses, or property within their jurisdiction to fund local public services and infrastructure.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:15 a.m.