Triple
T12398804
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wells notice process |
E296193
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regulatory enforcement procedure |
C6032
|
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: regulatory enforcement procedure Context triple: [Wells notice process, instanceOf, regulatory enforcement procedure]
-
A.
regulatory provision
A regulatory provision is a specific, authoritative rule or requirement established by a regulatory body to govern conduct, processes, or standards within a defined domain.
-
B.
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.
-
C.
regulatory activity
Regulatory activity is the process by which an entity establishes, interprets, or enforces rules and standards to guide or control the behavior of systems, organizations, or individuals.
-
D.
governmental procedure
chosen
A governmental procedure is a formally established sequence of actions, rules, and decision-making steps that public authorities follow to create, implement, or enforce laws and policies.
-
E.
government regulatory program
A government regulatory program is an organized set of rules, procedures, and enforcement mechanisms established by a public authority to oversee, control, or guide specific activities or sectors in order to achieve defined policy objectives and protect the public interest.
- 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_69d6ad9f464c81909db36d7e96e34b9e |
completed | April 8, 2026, 7:33 p.m. |
Created at: April 8, 2026, 9:54 p.m.