Triple
T1164570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Upper Manhattan |
E24571
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | region of Manhattan |
C7106
|
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: region of Manhattan Context triple: [Upper Manhattan, instanceOf, region of Manhattan]
-
A.
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.
-
B.
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.
-
C.
metropolitan district
A metropolitan district is an administrative or governmental region that encompasses a central city and its surrounding urban and suburban areas, managed as a single integrated unit for planning, services, and governance.
-
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.
metropolitan area
A metropolitan area is a densely populated urban region consisting of a central city and its surrounding suburbs and satellite communities, linked by economic, social, and infrastructural ties.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
Created at: March 1, 2026, 7:45 p.m.