Triple
T18655320
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boring Community Planning Organization |
E456048
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | community planning organization |
C20591
|
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 planning organization Context triple: [Boring Community Planning Organization, instanceOf, community planning organization]
-
A.
community organisation
chosen
A community organisation is a structured group of people who collaborate locally to address shared needs, interests, or issues and to improve the well-being of their community.
-
B.
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.
-
C.
community arts organization
A community arts organization is a nonprofit group that provides accessible arts programs, events, and resources to engage, educate, and empower local residents through creative expression.
-
D.
community development program
A community development program is an organized initiative designed to improve the social, economic, and environmental well-being of a specific community through collaborative planning, resource mobilization, and capacity-building activities.
-
E.
community-based program
A community-based program is an organized set of activities and services designed and delivered within a local community to address shared needs, build capacity, and improve well-being through active resident participation and local partnerships.
- 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_69d8d38ea1e88190997e9b231190ba6f |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:47 a.m.