Triple
T35391895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Toll Bridge Authority |
E1022962
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Washington State agency |
C2542
|
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: Washington State agency Context triple: [Washington Toll Bridge Authority, instanceOf, Washington State agency]
-
A.
state government agency
chosen
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
B.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
-
C.
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.
-
D.
New York State government agency component
A New York State government agency component is an organizational unit within a state agency, such as a division, bureau, or office, that performs specific statutory or administrative functions on behalf of the agency.
-
E.
Washington state park
A Washington state park is a designated public natural or historic area within the state of Washington that is managed by the state government for recreation, conservation, and education.
- 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_69f76df34ba48190bd80f0814cdcd540 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.