Triple
T3383899
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Massachusetts Contingency Plan |
E71250
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state regulatory framework |
C11529
|
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 regulatory framework Context triple: [Massachusetts Contingency Plan, instanceOf, state regulatory framework]
-
A.
regulatory framework
chosen
A regulatory framework is a structured set of rules, guidelines, and enforcement mechanisms established by authorities to govern behaviors, processes, and standards within a specific domain.
-
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 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.
-
D.
federal government framework
A federal government framework is a structural system that defines how power, responsibilities, and relationships are distributed and coordinated between a central authority and its constituent regional or state governments.
-
E.
regulatory authority
A regulatory authority is an official body empowered by law to create, implement, and enforce rules and standards within a specific domain to protect public interests and ensure compliance.
- 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_69ad85a8fd9c819095ecedf838d2bf1b |
completed | March 8, 2026, 2:20 p.m. |
Created at: March 8, 2026, 3:14 p.m.