Triple
T27027352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Rehabilitation and Liquidation |
E680823
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state regulatory division |
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: state regulatory division Context triple: [Division of Rehabilitation and Liquidation, instanceOf, state regulatory division]
-
A.
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.
-
B.
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.
-
C.
state administrative board
A state administrative board is a government-appointed body that oversees, regulates, and implements specific public policies or administrative functions within a state’s jurisdiction.
-
D.
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.
-
E.
environmental regulatory division
The environmental regulatory division is a governmental or organizational unit responsible for developing, implementing, and enforcing policies, standards, and compliance measures to protect the environment and public health.
- 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_69eeeb5566f08190813daf896fa3da04 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 27, 2026, 7:11 a.m.