Triple
T25035994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consumer Protection Division of Georgia Department of Agriculture |
E626978
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state regulatory unit |
C2929
|
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 unit Context triple: [Consumer Protection Division of Georgia Department of Agriculture, instanceOf, state regulatory unit]
-
A.
state regulatory agency
chosen
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.
state government agency
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.
-
C.
state register
A state register is a hardware storage element that holds the current state of a digital system or finite state machine, updating its contents synchronously with a clock signal.
-
D.
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.
-
E.
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.
- 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_69e2ff2a2c088190be513727ee8bfe78 |
completed | April 18, 2026, 3:48 a.m. |
Created at: April 18, 2026, 6:08 a.m.