Triple
T24622615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Living Cully collaborative |
E609452
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | neighborhood-based collaborative |
C20173
|
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: neighborhood-based collaborative Context triple: [Living Cully collaborative, instanceOf, neighborhood-based collaborative]
-
A.
neighborhood
A neighborhood is a geographically localized community within a larger city or town, characterized by shared residential spaces, social interactions, and common amenities.
-
B.
collaborative networks
chosen
Collaborative networks are interconnected groups of individuals or organizations that share resources, knowledge, and responsibilities to achieve common goals more effectively than they could independently.
-
C.
community-based mechanism
A community-based mechanism is a locally driven process or structure through which community members collectively identify, decide on, and implement actions to address shared needs or manage common resources.
-
D.
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.
-
E.
collaborative approach
A collaborative approach is a method of working in which multiple individuals or groups actively share ideas, responsibilities, and decision-making to achieve a common goal.
- 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_69e2c4d1d3708190a0f2dc6a3a8523bb |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:32 a.m.