Triple
T24293159
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joint Planning and Execution Community |
E605879
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | stakeholder community |
C24881
|
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: stakeholder community Context triple: [Joint Planning and Execution Community, instanceOf, stakeholder community]
-
A.
stakeholder group
chosen
A stakeholder group is a collection of individuals or organizations that share a common interest in, or are affected by, the decisions, activities, or outcomes of a project, organization, or system.
-
B.
multistakeholder organization
A multistakeholder organization is a collaborative governance structure that brings together diverse actors—such as governments, businesses, civil society, and experts—to jointly make decisions, set standards, or address complex issues of shared concern.
-
C.
Stʼatʼimc community
A Stʼatʼimc community is a group of people belonging to the Stʼatʼimc (Lillooet) Nation, connected by shared territory, language, culture, governance, and kinship within the Interior Plateau region of British Columbia.
-
D.
government stakeholder
A government stakeholder is any individual, agency, or institution within the public sector that has an interest in, influence over, or responsibility for a policy, program, or decision.
-
E.
community
A community is a group of people connected by shared location, interests, values, or identity who interact and support one another over time.
- 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_69e29549335881909cbf27adcaba1cf0 |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:09 a.m.