Triple
T8213621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DCWP |
E191881
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City government agency |
C11903
|
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 City government agency Context triple: [DCWP, instanceOf, New York City government agency]
-
A.
New York City agency
chosen
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.
-
B.
New York State government agency component
A New York State government agency component is an organizational unit within a state agency, such as a division, bureau, or office, that performs specific statutory or administrative functions on behalf of the agency.
-
C.
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.
-
D.
borough of New York City
A borough of New York City is one of the five primary administrative and geographic divisions of the city, each coextensive with a county and possessing its own local identity, governance structures, and community characteristics within the larger metropolis.
-
E.
New York State government document
A New York State government document is an official record, publication, or communication produced or issued by an agency, department, or office of the New York State government in the course of its public duties.
- 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_69ca82c8c054819087fedd9a5436b8a3 |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:44 p.m.