Triple
T22509781
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nottinghamshire voluntary and community organisations |
E556488
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | network of voluntary organisations |
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: network of voluntary organisations Context triple: [Nottinghamshire voluntary and community organisations, instanceOf, network of voluntary organisations]
-
A.
voluntary association
A voluntary association is an organized group formed and maintained by individuals who freely choose to join together to pursue shared interests, goals, or activities.
-
B.
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.
-
C.
nonprofit organization
A nonprofit organization is an entity formed for purposes other than generating profit, using any surplus revenues to further its mission or public benefit rather than distributing them to owners or shareholders.
-
D.
women's voluntary organization
A women's voluntary organization is a group formed and led primarily by women who collectively contribute their time, skills, and resources to advance social, cultural, educational, or charitable goals without financial compensation.
-
E.
youth organization network
A youth organization network is a collaborative structure that connects multiple youth-focused groups to share resources, coordinate activities, and amplify young people’s voices and impact.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:50 p.m.