Triple
T7404116
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Division of Administrative Rules |
E170822
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York State government 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: New York State government division Context triple: [Division of Administrative Rules, instanceOf, New York State government division]
-
A.
New York State program
A New York State program is an organized, state-administered initiative designed to deliver specific public services, benefits, or regulatory functions to residents, businesses, or communities within New York State.
-
B.
municipality in New York
A municipality in New York is a legally incorporated local government entity—such as a city, town, or village—established under New York State law to provide public services and governance within a defined geographic area.
-
C.
New York City agency
A New York City agency is a governmental organization responsible for administering and enforcing specific public services, regulations, and policies within the five boroughs of New York City.
-
D.
county of New York State
A county of New York State is a primary local government and administrative subdivision of the state, responsible for regional services such as law enforcement, courts, record-keeping, and certain social and infrastructure functions for its constituent municipalities and residents.
-
E.
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.
- 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_69c68a6010108190925e5284de022660 |
completed | March 27, 2026, 1:47 p.m. |
Created at: March 27, 2026, 3:10 p.m.