Triple
T21145008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia Corporations Division |
E521029
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state business filing office |
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 business filing office Context triple: [Georgia Corporations Division, instanceOf, state business filing office]
-
A.
state government office
A state government office is an administrative entity within a state’s governmental structure responsible for implementing specific public policies, services, and regulatory functions under the authority of state law.
-
B.
state council office
The state council office is an administrative body that supports the state council by coordinating policy implementation, managing governmental affairs, and providing organizational and logistical services.
-
C.
court office
A court office is an administrative unit within a judicial system responsible for managing case records, scheduling hearings, processing legal documents, and supporting the day-to-day operations of the court.
-
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.
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.
- 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_69e0b50c6a848190a4e525a77a319b8a |
completed | April 16, 2026, 10:08 a.m. |
Created at: April 16, 2026, 2:58 p.m.