Triple
T8213377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Uniform Land Use Review Procedure |
E191875
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | New York City government procedure |
C23696
|
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 procedure Context triple: [Uniform Land Use Review Procedure, instanceOf, New York City government procedure]
-
A.
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.
-
B.
New York City community board
A New York City community board is a local advisory group of appointed residents that consults on land use, budget, and service delivery issues within a specific community district.
-
C.
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.
-
D.
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.
-
E.
New York City Subway infrastructure project
A New York City Subway infrastructure project is a coordinated planning, construction, and modernization effort aimed at building, upgrading, or maintaining the physical and technological systems that support subway service across the city.
- F. None of above. chosen
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.