evokes

• CURIE: gmeow:evokes
• IRI: https://blackcatinformatics.ca/gmeow/evokes
• Category: property
• Defined by: gmeow:slices/inquiry
• Box roles: RBox role (What is this?)

Relates a declarative or erotetic premise to a question it gives rise to — Wiśniewski's erotetic implication (a question or set of propositions evokes a further question). The DOMAIN is left intentionally open: a gmeow:Proposition or a gmeow:Question may evoke a question, but asserting a domain (or an owl:unionOf) would prematurely close the surface, so it stays open and is documented in prose. NOT functional.

Structure

Property shape: object property; ? -> gmeow:Question

Practical Pattern

Use gmeow:evokes from ? to gmeow:Question when the relationship itself belongs in the native GMEOW graph.

Example Snippets

These snippets are generated from canonical slice examples and trimmed to the Turtle blocks where this term appears.

Known Unknown

• Source: slices/core/metacognition/examples/known-unknown.ttl
• Examples catalog: open in catalog#example-slices-core-metacognition-examples-known-unknown

# SPDX-FileCopyrightText: 2026 Blackcat Informatics® Inc. <paudley@blackcatinformatics.ca>
# SPDX-License-Identifier: CC-BY-4.0
#
# Worked example — a KNOWN-UNKNOWN that mints an inquiry, with NO new bridge term.
# Lillith recognises the boundary of her own knowledge (gmeow:awareOfNotKnowing),
# the second-order complement of the cognition knowledge spectrum. The recognised
# gap motivates a question by REUSING inquiry's open-domain gmeow:evokes (the
# not-known subject evokes the question) and the inquiry spine (gmeow:seeksToKnow)
# — there is no gmeow:motivates term (Principle 6), and the bridge to the inquiry
# slice is documented routing, not an entailment. This is the trustworthy-agent
# move: surfacing what it does not know as an open inquiry rather than confabulating.
@prefix gmeow: <https://blackcatinformatics.ca/gmeow/> .
@prefix ex:    <https://blackcatinformatics.ca/gmeow/examples/metacognition/> .
@prefix rdfs:  <http://www.w3.org/2000/01/rdf-schema#> .

# --- The gap evokes a question (reusing inquiry's open-domain gmeow:evokes — the
#     not-known subject sits legally in its subject position, so no new motivates
#     term is minted), which Lillith then holds open and seeks to know.
ex:protocolX gmeow:evokes ex:howDoesProtocolXWork .

Common Companion Terms

gmeow:Question

Usage Advice

Use when

• Use to decorate an inquiry graph with Wiśniewski erotetic implication — recording that one premise or question gives rise to a further question — when that derived structure is worth keeping explicit.

Avoid when

• Avoid expecting any entailment from it — it is a solver-layer decoration (Principle 12) with no reasoner semantics; the core never derives an evoked question — and avoid making it functional, since a premise may evoke several questions.

How to use

• Assert gmeow:evokes from a gmeow:Proposition or gmeow:Question to the gmeow:Question it raises; treat the edge as recorded structure for a solver to consume, never as a fact the reasoner will materialise.

Scope notes

• SOLVER-LAYER decoration (Principle 12): gmeow:evokes records Wiśniewski erotetic implication as an OPTIONAL decoration of an inquiry graph and carries NO reasoner / entailment semantics in core — the ontology never derives an evoked question, and no DL axiom enforces the relation. Whether one question genuinely evokes another is solver work, asserted here only as recorded structure.

Examples

• ex:whoCommittedIt gmeow:evokes ex:whatWasTheMotive.