Triple
T8245981
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington Growth Management Act |
E192849
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | growth management statute |
C251
|
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: growth management statute Context triple: [Washington Growth Management Act, instanceOf, growth management statute]
-
A.
statute
chosen
A statute is a formal written law enacted by a legislative body that establishes rules, obligations, or prohibitions within a governing jurisdiction.
-
B.
enabling statute
An enabling statute is a law passed by a legislature that grants authority to a government agency or entity to carry out specific functions, make regulations, or implement policies within defined limits.
-
C.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
D.
time, place, and manner regulation case
A time, place, and manner regulation case is a legal dispute that examines whether government restrictions on when, where, or how expression occurs are content-neutral, narrowly tailored to serve a significant governmental interest, and leave open ample alternative channels for communication.
-
E.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
- 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_69ca82de7b8c81908d8106f8a53cff9b |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:48 p.m.