Triple
T7331648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts State Building Code |
E169014
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state regulation |
C4528
|
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: state regulation Context triple: [Massachusetts State Building Code, instanceOf, state regulation]
-
A.
state policy
A state policy is a formal set of principles and rules adopted by a government to guide decisions and actions in specific public domains such as health, education, economy, or security.
-
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.
state government
A state government is the political organization and administrative apparatus that exercises authority, creates and enforces laws, and provides public services within a specific subnational region of a country.
-
D.
United States state law
chosen
United States state law is the body of legal rules, regulations, and judicial decisions enacted and applied by an individual U.S. state to govern conduct, resolve disputes, and organize governmental powers within its jurisdiction.
-
E.
state administration
State administration is the organized system of public institutions and officials responsible for implementing government policies, managing public services, and enforcing laws within a state's territory.
- 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_69c68a568a6481908f11e20db7bc8446 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:03 p.m.