Triple
T18791382
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Local Involvement Network |
E459521
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public involvement mechanism |
C26355
|
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: public involvement mechanism Context triple: [Local Involvement Network, instanceOf, public involvement mechanism]
-
A.
community-based mechanism
chosen
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.
-
B.
partnership mechanism
A partnership mechanism is a structured approach, process, or set of rules that governs how two or more parties collaborate, share resources, distribute responsibilities, and allocate benefits to achieve common objectives.
-
C.
public policy mechanism
A public policy mechanism is a structured tool, process, or instrument used by governments or public institutions to influence behavior, allocate resources, or achieve specific societal outcomes.
-
D.
redress mechanism
A redress mechanism is a structured process or system through which individuals or groups can seek remedy, correction, or compensation for grievances, harms, or rights violations.
-
E.
project-based mechanism
A project-based mechanism is a structured approach or system in which resources, incentives, and decision-making processes are organized around discrete projects to achieve specific goals or outcomes.
- 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_69d8d396f54c8190ba49db31e8743842 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.