Triple
T7582963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Advisory Neighborhood Commission 1D |
E179536
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Advisory Neighborhood Commission |
C5960
|
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: Advisory Neighborhood Commission Context triple: [Advisory Neighborhood Commission 1D, instanceOf, Advisory Neighborhood Commission]
-
A.
neighborhood association
A neighborhood association is a community-based organization formed by residents of a specific area to address local issues, coordinate activities, and advocate for the neighborhood’s interests.
-
B.
municipal advisory committee
chosen
A municipal advisory committee is a formally appointed group of community members that provides recommendations and expert input to local government officials on specific policy areas, projects, or issues.
-
C.
committee of the New York City Council
A committee of the New York City Council is a specialized subgroup of council members responsible for reviewing, holding hearings on, and making recommendations regarding legislation and oversight within a specific policy area affecting the city.
-
D.
civic precinct
A civic precinct is a designated urban area that concentrates key public institutions, government buildings, and community spaces to serve as a focal point for civic life and public services.
-
E.
city commission
A city commission is a governing body, typically composed of elected or appointed officials, responsible for making policy decisions, overseeing municipal services, and guiding the development and administration of a city.
- 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_69c69f327db881909a21ae3b156f8ded |
completed | March 27, 2026, 3:16 p.m. |
Created at: March 27, 2026, 3:52 p.m.