Triple
T10771875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manhattan Community District 3 |
E254099
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community board jurisdiction |
C6558
|
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 jurisdiction Context triple: [Manhattan Community District 3, instanceOf, community board jurisdiction]
-
A.
local board
chosen
A local board is a governing or advisory body composed of community representatives responsible for making decisions, setting policies, or providing oversight within a specific geographic area or jurisdiction.
-
B.
community area
A community area is a defined geographic region within a larger locality, characterized by shared social, economic, and physical features that influence the lives and interactions of its residents.
-
C.
municipal board
A municipal board is a local governing body composed of appointed or elected members responsible for making decisions, setting policies, and overseeing specific functions or services within a municipality.
-
D.
community
A community is a group of people connected by shared location, interests, values, or identity who interact and support one another over time.
-
E.
community plan area
A community plan area is a geographically defined section of a jurisdiction for which detailed land use, development, and infrastructure policies are established to guide local growth and community character.
- 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_69d6aa5f54f4819082d0bbcb6f8797e6 |
completed | April 8, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:16 p.m.