Triple
T15462466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Queens Community District 13 |
E371937
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community board district of New York City |
C1188
|
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: community board district of New York City Context triple: [Queens Community District 13, instanceOf, community board district of New York City]
-
A.
New York City community board
chosen
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.
-
B.
New York City Council district
A New York City Council district is a geographically defined area of New York City represented by an elected council member responsible for legislating, budgeting, and overseeing local services for its residents.
-
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.
neighborhood in New York City
A neighborhood in New York City is a distinct, localized area within one of the city’s boroughs, characterized by its own social, cultural, architectural, and economic identity.
-
E.
Brooklyn neighborhood
A Brooklyn neighborhood is a distinct urban area within the borough of Brooklyn characterized by its unique blend of residential streets, local businesses, cultural communities, and architectural styles.
- 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_69d85cc8bd308190886949510b42e764 |
completed | April 10, 2026, 2:13 a.m. |
Created at: April 10, 2026, 3:32 a.m.