<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>Language on Moonment</title><link>https://moonment.net/en/tags/language/</link><description>Moon's notes on concepts, real projects, and reasoning open to review.</description><generator>Hugo</generator><language>en-US</language><managingEditor>Moon</managingEditor><webMaster>Moon</webMaster><copyright>© 2026 Moonment</copyright><lastBuildDate>Tue, 29 Sep 2026 15:04:00 +0800</lastBuildDate><atom:link href="https://moonment.net/en/tags/language/index.xml" rel="self" type="application/rss+xml"/><item><title>Concepts: How We Classify and Understand the World</title><link>https://moonment.net/en/notes/what-is-a-concept/</link><pubDate>Tue, 29 Sep 2026 12:57:00 +0800</pubDate><dc:creator>Moon</dc:creator><guid>https://moonment.net/en/notes/what-is-a-concept/</guid><description>Concepts make recognition, classification, and inference possible. This essay separates concepts, words, and objects, then examines intension, extension, prototypes, boundaries, counterexamples, and revision.</description><content:encoded><![CDATA[<p>A concept enables a thinker to treat different encounters as instances of a kind. We meet individual trees, purchases, emotions, products, and utterances. Conceptual capacities allow us to recognize them as trees, transactions, anger, products, or expressions of intention.</p>
<blockquote>
<p><strong>A concept is not the object itself. It is part of the way an object becomes intelligible as something.</strong></p>
</blockquote>
<p>This essay asks what a concept is, how its boundaries form, and how counterexamples can revise it. <a href="/en/notes/words-concepts-and-objects/">Words, Concepts, and Objects</a> examines expression and reference; <a href="/en/notes/conceptual-and-logical-thinking/">Conceptual and Logical Thinking</a> follows the use of concepts in judgment.</p>
<p>This gives concepts a double role. They reduce complexity enough for thought and communication, but every reduction highlights some differences and ignores others. Concepts make knowledge possible, and poorly formed concepts make systematic error possible.</p>
<h2 id="concepts-words-and-objects-are-different">Concepts, words, and objects are different</h2>
<p>A word is a public expression. A concept is the content or capacity involved in understanding and using such expressions. An object is what the expression and concept may concern.</p>
<table>
  <thead>
      <tr>
          <th>Level</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>object</td>
          <td>a particular phone</td>
      </tr>
      <tr>
          <td>expression</td>
          <td>the word <em>product</em></td>
      </tr>
      <tr>
          <td>conceptual content</td>
          <td>an organized capability or experience made available to users</td>
      </tr>
  </tbody>
</table>
<p>The three levels do not map one-to-one.</p>
<p>One word can express several concepts. <em>Product</em> may mean a manufactured item, the output of an operation, a market offering, or a managed digital service. Several expressions can also approach the same conceptual content. And a concept can represent something that does not exist, such as a unicorn, an ideal circle, or a fictional institution.</p>
<p>Consulting a dictionary is therefore only a beginning. Conceptual analysis also asks what is included, what is excluded, which contrasts matter, and whether the same expression changes meaning during an argument.</p>
<h2 id="three-philosophical-accounts-of-concepts">Three philosophical accounts of concepts</h2>
<p>Contemporary philosophy does not offer one uncontested ontology of concepts. Three families of views organize much of the debate.</p>
<h3 id="concepts-as-mental-representations">Concepts as mental representations</h3>
<p>On a representational view, concepts are components of mental states that carry content. They help explain how a person can think about cats in their absence, combine CAT with other concepts, and draw new conclusions.</p>
<p>A representation need not be a vivid inner picture. It may be symbolic, prototype-like, schematic, or distributed across a cognitive system. What matters is that it represents something and participates in cognition. Mental representation is consequently a central theoretical construct in cognitive science.<a href="https://plato.stanford.edu/entries/mental-representation/">Stanford Encyclopedia of Philosophy: Mental Representation</a></p>
<h3 id="concepts-as-abilities">Concepts as abilities</h3>
<p>An ability view emphasizes what a competent thinker can do. Possessing the concept CAT may involve discriminating cats from relevant non-cats, understanding claims about cats, and drawing appropriate inferences.</p>
<p>This account explains why repeating a definition is insufficient evidence of understanding. Concept possession appears in recognition, application, explanation, and inference.</p>
<h3 id="concepts-as-abstract-objects">Concepts as abstract objects</h3>
<p>An abstract-object view treats concepts as shareable contents rather than private mental episodes. Two people can think about the same concept even though their neural and psychological states differ. Mathematical, legal, and scientific concepts can remain available within a public practice after particular individuals forget them.</p>
<p>The Stanford Encyclopedia of Philosophy presents mental representations, abilities, and abstract objects as the three leading options. They emphasize psychological realization, competent use, and public content respectively.<a href="https://plato.stanford.edu/entries/concepts/">Stanford Encyclopedia of Philosophy: Concepts</a></p>
<p>These positions need not be casually collapsed into one theory. They answer different questions: what realizes a concept in a mind, what possessing it enables an agent to do, and what makes conceptual content shareable.</p>
<h2 id="intension-extension-and-boundary">Intension, extension, and boundary</h2>
<p>The <strong>intension</strong> of a concept concerns the properties, conditions, and relations used to characterize it. The <strong>extension</strong> concerns the things to which it applies.</p>
<p>For a concept such as COMMODITY, the intension might include availability for exchange under economic conditions. Its extension may include food, clothing, subscriptions, and standardized services.</p>
<p>Changing the intension commonly changes the extension. Requiring physical form would remove software from the extension. Removing exchange conditions might make almost every useful object a commodity.</p>
<p>The boundary between inclusion and exclusion is often where the real analysis begins:</p>
<ul>
<li>Is free software a product?</li>
<li>Is personal data a commodity?</li>
<li>Is an informal promise a contract?</li>
<li>Is a simulated agent an entity?</li>
</ul>
<p>Boundary cases reveal assumptions hidden by central examples.</p>
<h2 id="definitions-and-prototypes-do-different-work">Definitions and prototypes do different work</h2>
<p>Some concepts are governed by explicit criteria. Others are organized partly around prototypes and family resemblances.</p>
<p>A sparrow is a prototypical bird. A penguin is still a bird despite lacking the prototype&rsquo;s ability to fly. Prototype-based recognition is fast and useful, but a prototype is not automatically a definition.</p>
<p>This distinction matters in product design, law, and AI. A model trained on typical cases can fail on valid but unusual cases. A policy based only on familiar examples can exclude people or situations that satisfy the actual standard.</p>
<p>Definitions also differ in purpose. A lexical definition reports established usage. A stipulative definition introduces a usage for a particular inquiry. A theoretical definition situates something inside an explanatory theory. A legal or institutional definition may help constitute a status.</p>
<p>Asking “What is the correct definition?” is incomplete until the purpose and domain are specified.</p>
<h2 id="concepts-form-networks">Concepts form networks</h2>
<p>Concepts rarely function as isolated entries. They occupy inferential and practical networks:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">need → goal → intention → action
</span></span><span class="line"><span class="cl">need → product → commodity → exchange
</span></span><span class="line"><span class="cl">fact → judgment → inference → decision
</span></span><span class="line"><span class="cl">value → principle → rule → constraint
</span></span></code></pre></div><p>To understand a concept is partly to understand what follows from applying it, what would count against applying it, and how it differs from neighboring categories.</p>
<p>This is why a topic word can serve as an index entry without yet being a developed concept. A useful concept record needs distinctions, criteria, examples, counterexamples, relations, and revision conditions.</p>
<h2 id="concepts-represent-more-than-objects">Concepts represent more than objects</h2>
<p>Concepts can concern different ontological and grammatical categories:</p>
<table>
  <thead>
      <tr>
          <th>Kind</th>
          <th>Examples</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>entities</td>
          <td>person, company, product</td>
      </tr>
      <tr>
          <td>events</td>
          <td>election, purchase, collision</td>
      </tr>
      <tr>
          <td>actions</td>
          <td>choosing, buying, inferring</td>
      </tr>
      <tr>
          <td>states</td>
          <td>anger, poverty, stability</td>
      </tr>
      <tr>
          <td>properties</td>
          <td>legal, rational, positive</td>
      </tr>
      <tr>
          <td>relations</td>
          <td>causation, competition, ownership</td>
      </tr>
      <tr>
          <td>processes</td>
          <td>learning, evolution, production</td>
      </tr>
      <tr>
          <td>quantitative structures</td>
          <td>probability, expected value</td>
      </tr>
      <tr>
          <td>normative structures</td>
          <td>rules, principles, responsibility</td>
      </tr>
      <tr>
          <td>abstract organizations</td>
          <td>systems, logics, strategies</td>
      </tr>
  </tbody>
</table>
<p>Treating every concept as a name for a thing produces category mistakes. Causation is not another physical object sitting beside causes and effects. Probability is not located somewhere in space. Responsibility may depend on relations among agents, norms, knowledge, and control.</p>
<h2 id="how-concepts-are-formed">How concepts are formed</h2>
<p>No single process explains every concept. Concept formation can involve:</p>
<ul>
<li>perceptual discrimination among recurring features;</li>
<li>abstraction from particular instances;</li>
<li>classification under learned categories;</li>
<li>linguistic correction within a social practice;</li>
<li>embodied interaction and practical feedback;</li>
<li>institutional rules that create statuses;</li>
<li>scientific theories that reorganize ordinary categories.</li>
</ul>
<p>Some concepts are learned through repeated examples. Some are explicitly defined. Some are created by institutions. Others change when a theory explains why familiar classifications were misleading.</p>
<p>Scientific concepts illustrate the difference between preserving a word and preserving a concept. Everyday language may keep the word <em>heat</em> while physics gives it a more precise theoretical role. Conceptual continuity cannot be inferred from verbal continuity alone.</p>
<h2 id="why-conceptual-disputes-persist">Why conceptual disputes persist</h2>
<p>At least four kinds of disagreement are easily conflated.</p>
<p>First, speakers may attach different criteria to the same word. One person may define a product by production, another by user value, and another by market offering.</p>
<p>Second, the category itself may have vague boundaries. <em>Game</em>, <em>art</em>, <em>intelligence</em>, and <em>consciousness</em> resist simple criteria that cover every accepted case.</p>
<p>Third, descriptive and evaluative content may be mixed. <em>Normal</em>, <em>successful</em>, <em>progressive</em>, and <em>civilized</em> can describe patterns while also conveying approval.</p>
<p>Fourth, disciplines may construct different concepts for different explanatory purposes. <em>Entity</em> does different work in metaphysics, databases, natural-language processing, and law.</p>
<p>Good analysis does not erase these differences. It states which concept is being used, in which domain, for which purpose, and with which exclusions.</p>
<h2 id="reification-and-other-conceptual-errors">Reification and other conceptual errors</h2>
<p>Conceptual mistakes take recurring forms:</p>
<ul>
<li><strong>word-object confusion</strong>: assuming that every noun names a separate entity;</li>
<li><strong>equivocation</strong>: shifting a term&rsquo;s meaning during an argument;</li>
<li><strong>category mistake</strong>: asking of one kind of thing a question appropriate to another;</li>
<li><strong>reification</strong>: treating an abstraction such as “the market” as a unified intentional agent;</li>
<li><strong>unwarranted essentialism</strong>: assuming every useful category has one timeless hidden essence;</li>
<li><strong>prototype substitution</strong>: treating a familiar example as the full criterion;</li>
<li><strong>descriptive-normative collapse</strong>: inferring what ought to be from what is common;</li>
<li><strong>level confusion</strong>: mixing an object, a model of the object, and an evaluation of the model.</li>
</ul>
<p>These errors cannot always be repaired by gathering more data. Sometimes the categories used to organize the data must be repaired first.</p>
<h2 id="a-method-for-analyzing-a-concept">A method for analyzing a concept</h2>
<p>A reusable inquiry can ask:</p>
<ol>
<li>Which expressions are used for the concept?</li>
<li>What kinds of entities, events, properties, or relations does it concern?</li>
<li>How do ordinary and specialized uses differ?</li>
<li>What criteria make up its intension?</li>
<li>What central cases belong to its extension?</li>
<li>Which boundary cases are difficult?</li>
<li>Which neighboring concepts must be separated?</li>
<li>Which counterexamples challenge the current account?</li>
<li>What cognitive or practical work does the concept perform?</li>
<li>What evidence or practice would justify revising it?</li>
</ol>
<p>Conceptual analysis is not the search for a sentence immune to change. It builds a public, usable distinction and specifies how reality can correct it.</p>
<h2 id="conclusion">Conclusion</h2>
<p>Concepts let finite thinkers move beyond isolated experiences. They make recognition, communication, judgment, and inquiry possible.</p>
<p>Every concept also selects. It makes some differences visible and leaves others in the background. Responsible concept use therefore requires criteria, boundaries, contrasts, counterexamples, and revision.</p>
<blockquote>
<p><strong>To possess a concept is not merely to know a word. It is to identify, distinguish, apply, infer, and revise with it.</strong></p>
</blockquote>
]]></content:encoded></item><item><title>Entities: Identity, Reference, and AI Systems</title><link>https://moonment.net/en/notes/what-is-an-entity/</link><pubDate>Thu, 24 Sep 2026 16:31:31 +0800</pubDate><dc:creator>Moon</dc:creator><guid>https://moonment.net/en/notes/what-is-an-entity/</guid><description>An entity is something treated as having a distinguishable identity. This essay separates mentions, names, classes, records, and real-world referents across philosophy and AI.</description><content:encoded><![CDATA[<p>People, companies, cities, products, documents, events, and fictional characters are very different kinds of things. Yet an information system may treat all of them as entities.</p>
<p>The word is broad because it does not describe a particular material composition. It describes a role within thought, language, or a model:</p>
<blockquote>
<p><strong>An entity is something treated as having a distinguishable identity, so that it can be referred to, described, related to other things, tracked over time, or acted upon.</strong></p>
</blockquote>
<p>An entity need not be tangible. It need not exist independently. It need not even exist in the actual world. What it needs, within a particular domain, is enough identity for the system to treat it as the same subject across multiple statements or operations.</p>
<h2 id="where-does-the-word-entity-come-from">Where does the word “entity” come from?</h2>
<p>English <code>entity</code> comes through Medieval Latin <code>entitas</code>, formed from <code>ens</code>, a being or something that is, which in turn is related to the Latin verb <code>esse</code>, to be. The word therefore carries an ontological background: it concerns something considered as a being or item of existence.<a href="https://www.ahdictionary.com/word/search.html?q=entity">American Heritage Dictionary: entity</a></p>
<p>That history explains why <code>entity</code> can be used so widely. It may refer to a physical object, a person, an institution, an event, a number, a proposition, or another item admitted by a theory. In philosophy, <code>thing</code>, <code>being</code>, <code>entity</code>, and <code>object</code> may all compete for the role of a maximally general term for whatever a system acknowledges.<a href="https://plato.stanford.edu/entries/object/">Stanford Encyclopedia of Philosophy: Object</a></p>
<p>No single list of entities is philosophically neutral. A physicalist ontology, a mathematical ontology, a legal ontology, and a fictional world may recognize different kinds of things. Calling something an entity is therefore both a semantic move and, in many contexts, an ontological commitment.</p>
<h2 id="an-entity-is-not-merely-a-physical-object">An entity is not merely a physical object</h2>
<p>A physical object usually has material structure and some spatial boundary. An entity need not.</p>
<p>A corporation has no single body. It depends on law, records, roles, property, contracts, and continued institutional recognition. A meeting is not a durable object, but it can have participants, a time, a location, an agenda, and an outcome. An account exists only within a platform and its rules, yet the platform must still distinguish one account from another.</p>
<p>All three can function as entities because each can be identified and become the subject of further claims.</p>
<p>The English words <code>entity</code> and <code>substance</code> should also be separated. An entity is any item treated as a being or object of reference. A substance, in major philosophical traditions, is more specifically something taken to exist relatively independently or to bear properties. Events, relations, numbers, and properties may count as entities without counting as substances in that stronger sense.<a href="https://plato.stanford.edu/entries/substance/">Stanford Encyclopedia of Philosophy: Substance</a></p>
<h2 id="reference-does-not-establish-real-existence">Reference does not establish real existence</h2>
<p>Sherlock Holmes can be named, described, compared with other characters, and placed in a network of fictional relations. He is an entity in literary discourse and may be an entity in a knowledge base. None of this makes him a historical person.</p>
<p>At least three questions must therefore remain separate:</p>
<table>
  <thead>
      <tr>
          <th>Level</th>
          <th>Question</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Discourse entity</td>
          <td>Has language introduced something that can be referred to again?</td>
      </tr>
      <tr>
          <td>Model entity</td>
          <td>Does an information system represent it as a distinct item?</td>
      </tr>
      <tr>
          <td>Real-world entity</td>
          <td>Is there sufficient evidence for a corresponding thing in the actual world?</td>
      </tr>
  </tbody>
</table>
<p>An entity can exist at the first two levels without satisfying the third. Plans, hypothetical products, possible events, mistaken identities, and fictional characters all demonstrate why representation and reality must not be collapsed.</p>
<h2 id="identity-is-the-central-problem">Identity is the central problem</h2>
<p>Finding a noun is easy. Determining what makes something the same entity is harder.</p>
<p>A person may change names and addresses while remaining the same person. A corporation may replace every employee and continue as the same legal organization. An article may be revised many times while retaining one publication history. A product may keep its commercial name while its capabilities, components, or terms change substantially.</p>
<p>Different types of entities require different <strong>identity criteria</strong>:</p>
<table>
  <thead>
      <tr>
          <th>Entity type</th>
          <th>Possible basis of identity</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Person</td>
          <td>legal records, bodily and biographical continuity</td>
      </tr>
      <tr>
          <td>Corporation</td>
          <td>legal registration, organizational and contractual continuity</td>
      </tr>
      <tr>
          <td>Document</td>
          <td>identifier, provenance, content hash, or version history</td>
      </tr>
      <tr>
          <td>Article</td>
          <td>authorship and publication lineage, slug, revision history</td>
      </tr>
      <tr>
          <td>Product model</td>
          <td>model definition, capability boundary, specification</td>
      </tr>
      <tr>
          <td>Commercial item</td>
          <td>SKU, serial number, batch, or unit of sale</td>
      </tr>
      <tr>
          <td>Online account</td>
          <td>platform, stable account ID, control and authentication</td>
      </tr>
      <tr>
          <td>Event</td>
          <td>participants, time, place, and occurrence structure</td>
      </tr>
  </tbody>
</table>
<p>A name is not an identity. Two people can share a name, and one person can use several names. A set of properties is not automatically an identity either. Properties change, records conflict, and two objects may resemble one another closely without being the same object.</p>
<p>A useful entity representation usually needs more than a label:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">stable identifier
</span></span><span class="line"><span class="cl">+ entity type
</span></span><span class="line"><span class="cl">+ attributes
</span></span><span class="line"><span class="cl">+ relationships
</span></span><span class="line"><span class="cl">+ temporal state
</span></span><span class="line"><span class="cl">+ provenance
</span></span><span class="line"><span class="cl">+ confidence in the identity match
</span></span></code></pre></div><h2 id="how-does-ontology-relate-to-entities">How does ontology relate to entities?</h2>
<p>An entity does not become a useful modeling unit in isolation. A system must decide what kinds of entities it recognizes, which attributes they may have, which relations may connect them, and what counts as persistence or change.</p>
<p>Those decisions form part of an ontology.</p>
<blockquote>
<p><strong>An entity is a particular item recognized within a domain; an ontology states which kinds of items the domain recognizes and how they may be organized.</strong></p>
</blockquote>
<p>“Shanghai” may be stored as a string in a simple customer table. In a geographical knowledge system, it may be represented as an entity with coordinates, administrative status, districts, and relationships to other places. The difference depends on whether the system needs to identify Shanghai independently and reason about it.</p>
<p>Philosophical ontology asks what exists and how different kinds of beings exist. Computational ontology turns a domain commitment into an explicit model of classes, entities, properties, relations, and constraints. A fuller account appears in <a href="/en/notes/what-is-ontology/">“What Is Ontology? From What Exists to Models AI Can Use”</a>. Here ontology matters because it supplies the type system and identity conditions within which entities can be distinguished.</p>
<h2 id="what-does-entity-mean-in-ai">What does “entity” mean in AI?</h2>
<p>In AI, an entity is usually an object distinguished from text, images, records, or an environment because the system needs to understand, retrieve, remember, reason about, or act on it.</p>
<p>The term changes meaning across tasks. Named-entity recognition, entity linking, entity resolution, knowledge graphs, computer vision, databases, and AI agents do not operate at exactly the same level.</p>
<h2 id="named-entity-recognition-finds-mentions-not-verified-objects">Named-entity recognition finds mentions, not verified objects</h2>
<p>Consider the sentence:</p>
<blockquote>
<p>Apple plans to announce a new phone in Shanghai tomorrow.</p>
</blockquote>
<p>A named-entity recognition system may label:</p>
<ul>
<li><code>Apple</code> as an organization;</li>
<li><code>Shanghai</code> as a location;</li>
<li><code>tomorrow</code> as a date.</li>
</ul>
<p>At this stage, the system has identified <strong>mentions</strong>: spans of language that appear to refer to named or otherwise categorized entities. In engineering terms, a conventional NER component predicts labeled token spans. spaCy, for example, describes its entity recognizer as identifying non-overlapping labeled spans.<a href="https://spacy.io/api/entityrecognizer/">spaCy: EntityRecognizer</a></p>
<p>The output does not yet prove that <code>Apple</code> refers to Apple Inc. rather than a different organization, a title, or an annotation mistake. Nor does it establish that the announced phone is a particular product with a known identity.</p>
<p>The distinction is fundamental:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">entity mention ≠ entity identity
</span></span><span class="line"><span class="cl">entity name ≠ unique referent
</span></span><span class="line"><span class="cl">entity type ≠ proof of existence
</span></span></code></pre></div><h2 id="entity-linking-connects-a-mention-to-a-canonical-entity">Entity linking connects a mention to a canonical entity</h2>
<p>Entity linking attempts to determine which known entity a mention refers to.</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">“Apple” in a sentence
</span></span><span class="line"><span class="cl">        ↓ disambiguation
</span></span><span class="line"><span class="cl">Apple Inc.
</span></span><span class="line"><span class="cl">        ↓ normalization
</span></span><span class="line"><span class="cl">knowledge-base ID: company/apple-inc
</span></span></code></pre></div><p>This requires at least two forms of reasoning:</p>
<ul>
<li><strong>Disambiguation:</strong> Which entity with this name fits the context?</li>
<li><strong>Coreference and normalization:</strong> Do <code>Apple</code>, <code>Apple Inc.</code>, and <code>the Cupertino company</code> refer to the same entity here?</li>
</ul>
<p>Linking converts a piece of language into an addressable object in a knowledge system. It is still fallible. The selected knowledge-base entry may be wrong, duplicated, incomplete, or out of date.</p>
<h2 id="entity-resolution-asks-whether-records-describe-the-same-thing">Entity resolution asks whether records describe the same thing</h2>
<p>Entity linking usually begins with language and a knowledge base. <strong>Entity resolution</strong> often begins with records.</p>
<p>A customer system may contain:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Li Ming, Shanghai, 138****1234
</span></span><span class="line"><span class="cl">Ming Li, 上海市, 138****1234
</span></span><span class="line"><span class="cl">李明, Pudong, 138****1234
</span></span></code></pre></div><p>Do these records describe one person, two people, or three? Shared fields provide evidence, but they do not make the answer automatic. Phone numbers can be reassigned, addresses can be shared, and names can collide.</p>
<p>Entity resolution may involve:</p>
<ul>
<li>deduplicating records;</li>
<li>matching aliases and transliterations;</li>
<li>detecting that one entity has split or merged in a source system;</li>
<li>preserving conflicting claims rather than forcing a premature merge;</li>
<li>recording why two records were considered the same.</li>
</ul>
<p>This is an identity decision under uncertainty. A useful system keeps the evidence and confidence behind the match instead of treating similarity as certainty.</p>
<h2 id="knowledge-graphs-place-entities-in-a-network-of-claims">Knowledge graphs place entities in a network of claims</h2>
<p>In a knowledge graph, entities are commonly represented as nodes connected by typed relations:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Apple Inc. ──headquartered in──&gt; Cupertino
</span></span><span class="line"><span class="cl">Apple Inc. ──released──&gt; iPhone
</span></span><span class="line"><span class="cl">iPhone ──instance of──&gt; smartphone product
</span></span></code></pre></div><p>This representation distinguishes:</p>
<ul>
<li>entities such as Apple Inc., Cupertino, and an iPhone model;</li>
<li>classes such as company, city, and product;</li>
<li>attributes such as dates and names;</li>
<li>relations such as <code>headquartered in</code> and <code>released</code>.</li>
</ul>
<p>RDF represents claims as subject–predicate–object triples. Its notion of a resource is deliberately broad: a resource may denote a physical thing, a document, an abstract concept, or another item in the universe of discourse.<a href="https://www.w3.org/TR/rdf11-concepts/">W3C: RDF 1.1 Concepts and Abstract Syntax</a></p>
<p>An ontology supplies general rules, while a knowledge graph contains particular claims:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">ontology: a company may release a product
</span></span><span class="line"><span class="cl">claim: Apple Inc. released a particular iPhone model
</span></span></code></pre></div><p>A graph node is not automatically a verified real-world object. It may represent a class, a fictional entity, a planned object, an uncertain hypothesis, or an erroneous record. Provenance and status remain necessary.</p>
<h2 id="concepts-classes-entities-identifiers-and-records">Concepts, classes, entities, identifiers, and records</h2>
<p>Several layers are easily confused:</p>
<table>
  <thead>
      <tr>
          <th>Layer</th>
          <th>What does it provide?</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Word or phrase</td>
          <td>an expression used in language</td>
      </tr>
      <tr>
          <td>Name</td>
          <td>a conventional way to refer to something</td>
      </tr>
      <tr>
          <td>Concept</td>
          <td>a general structure used to understand things</td>
      </tr>
      <tr>
          <td>Class</td>
          <td>a modeled category of possible members</td>
      </tr>
      <tr>
          <td>Entity</td>
          <td>the particular item currently referred to</td>
      </tr>
      <tr>
          <td>Identifier</td>
          <td>a stable handle used by a system</td>
      </tr>
      <tr>
          <td>Record</td>
          <td>stored claims about an entity</td>
      </tr>
      <tr>
          <td>Real-world referent</td>
          <td>whatever, if anything, exists beyond the model</td>
      </tr>
  </tbody>
</table>
<p><code>Company</code> may be a concept and a class. Apple Inc. may be an entity. <code>Apple</code> may be a name or mention. <code>company_001</code> may be an internal identifier. A row in a database may contain claims about the company. None of these layers is identical to the organization itself.</p>
<p>One entity may have many names and records. One record may accidentally combine facts about several entities. A unique database key guarantees uniqueness inside a table; it does not prove that the row corresponds correctly to one real-world thing.</p>
<h2 id="when-should-something-be-modeled-as-an-entity">When should something be modeled as an entity?</h2>
<p>Not every noun phrase needs its own entity. Six questions help:</p>
<ol>
<li><strong>Does it need a distinct identity?</strong> Must the system distinguish this item from similar items?</li>
<li><strong>Will it be referred to repeatedly?</strong> Will multiple documents, records, or tasks mention it?</li>
<li><strong>Does it have its own attributes?</strong> Must the system store a status, date, location, or owner?</li>
<li><strong>Does it participate in relationships?</strong> Must it be connected to other objects?</li>
<li><strong>Does it persist through time?</strong> Must the system recognize it after some properties change?</li>
<li><strong>Can the system act on it?</strong> Will it be queried, edited, sent, authorized, purchased, deleted, or monitored?</li>
</ol>
<p>If most answers are yes, an entity is often appropriate. Otherwise a literal value, label, or temporary span may be enough.</p>
<p>Entity modeling is not free. Every entity type introduces identity rules, lifecycle questions, merge and split behavior, provenance requirements, and access-control consequences.</p>
<h2 id="can-events-states-and-intentions-become-entities">Can events, states, and intentions become entities?</h2>
<p>Grammatical categories do not map directly onto model categories. Nouns do not always denote entities, and verbs do not always remain mere relations.</p>
<p>“Maya signed Contract C36” can be represented as a simple relation:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Maya ──signed──&gt; Contract C36
</span></span></code></pre></div><p>If the system must record the date, location, version, witnesses, method, and legal status, the signing can become an event entity:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">Signing Event E1024
</span></span><span class="line"><span class="cl">├── signer: Maya
</span></span><span class="line"><span class="cl">├── object: Contract C36
</span></span><span class="line"><span class="cl">├── time: 2026-09-24
</span></span><span class="line"><span class="cl">├── place: Shanghai
</span></span><span class="line"><span class="cl">└── status: effective
</span></span></code></pre></div><p>An intention can likewise be modeled as a mental-state entity when the system needs to record whose intention it is, what outcome it concerns, when it was inferred, which evidence supports the inference, and how uncertain the interpretation remains.</p>
<p>Reification makes an event, relation, or state available for further description. It is useful when the system needs that detail, but it should not be mistaken for a discovery that the world naturally divides itself in exactly that form.</p>
<h2 id="how-do-large-language-models-handle-entities">How do large language models handle entities?</h2>
<p>A standard large language model receives tokens and computes distributed representations shaped by training data and current context. It can learn that <code>Apple</code> often occurs near company, product, iPhone, and Cupertino, and it can frequently disambiguate the word from the fruit.</p>
<p>This competence does not imply that the model contains a single, explicit, canonical Apple Inc. record comparable to a carefully maintained knowledge base. Entity information may be distributed across parameters and reconstructed probabilistically in context.</p>
<p>Consequently, a language model may:</p>
<ul>
<li>resolve an entity correctly in one context and confuse it in another;</li>
<li>conflate a company, its brand, its products, and its website;</li>
<li>recall an old property without knowing that it has changed;</li>
<li>invent a plausible person, paper, organization, or product;</li>
<li>answer without a stable source for the entity claim.</li>
</ul>
<p>For tasks that require reliable action, model output is usually only one layer:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">language model
</span></span><span class="line"><span class="cl">+ domain ontology
</span></span><span class="line"><span class="cl">+ entity IDs and resolution
</span></span><span class="line"><span class="cl">+ current state and provenance
</span></span><span class="line"><span class="cl">+ time-aware records
</span></span><span class="line"><span class="cl">+ permissions and action rules
</span></span></code></pre></div><p>The language model interprets open-ended language. The ontology defines possible types and relations. Entity services determine identity. Data sources establish current state. Authorization determines which operations are permitted.</p>
<h2 id="why-do-ai-agents-need-explicit-entity-identity">Why do AI agents need explicit entity identity?</h2>
<p>Consider the instruction:</p>
<blockquote>
<p>Update yesterday’s article about needs on Moonment.</p>
</blockquote>
<p>The request contains several unresolved references:</p>
<table>
  <thead>
      <tr>
          <th>Expression</th>
          <th>Entity question</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>yesterday</td>
          <td>Which timezone and time interval?</td>
      </tr>
      <tr>
          <td>the article about needs</td>
          <td>Which document and slug?</td>
      </tr>
      <tr>
          <td>update</td>
          <td>Edit a draft, commit a repository, or publish a website?</td>
      </tr>
      <tr>
          <td>Moonment</td>
          <td>Which project, repository, deployment, and domain?</td>
      </tr>
      <tr>
          <td>article version</td>
          <td>Chinese, English, or both?</td>
      </tr>
      <tr>
          <td>requesting user</td>
          <td>Which permissions and prior authorization apply?</td>
      </tr>
  </tbody>
</table>
<p>The agent may understand the general intention while still acting on the wrong file, project, account, language version, or deployment.</p>
<p>A safer path is:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">natural-language request
</span></span><span class="line"><span class="cl">        ↓
</span></span><span class="line"><span class="cl">mention and reference detection
</span></span><span class="line"><span class="cl">        ↓
</span></span><span class="line"><span class="cl">type assignment and coreference
</span></span><span class="line"><span class="cl">        ↓
</span></span><span class="line"><span class="cl">entity linking and resolution
</span></span><span class="line"><span class="cl">        ↓
</span></span><span class="line"><span class="cl">relation, event, and intent interpretation
</span></span><span class="line"><span class="cl">        ↓
</span></span><span class="line"><span class="cl">state, provenance, and authorization checks
</span></span><span class="line"><span class="cl">        ↓
</span></span><span class="line"><span class="cl">action on the resolved entity
</span></span></code></pre></div><p>Intent specifies the change the user appears to seek. Entity resolution determines what the intended action applies to. Authorization determines whether the action may be performed. None can substitute for the others.</p>
<h2 id="can-ai-establish-that-an-entity-really-exists">Can AI establish that an entity really exists?</h2>
<p>Language alone cannot establish existence.</p>
<p>An AI system can estimate that a phrase is probably a person’s name, that context probably indicates a company, or that a mention probably links to a known record. Real-world verification requires additional evidence, such as:</p>
<ul>
<li>an authoritative registry or primary source;</li>
<li>a current database record;</li>
<li>a file that actually exists in the relevant filesystem;</li>
<li>a live website or API;</li>
<li>an authenticated identity and permission system;</li>
<li>a sensor observation or human confirmation.</li>
</ul>
<p>The following claims are distinct:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">the text mentions something
</span></span><span class="line"><span class="cl">≠ the model identified it correctly
</span></span><span class="line"><span class="cl">≠ the system linked the correct record
</span></span><span class="line"><span class="cl">≠ the record is accurate and current
</span></span><span class="line"><span class="cl">≠ the corresponding thing exists now
</span></span><span class="line"><span class="cl">≠ the user is authorized to act on it
</span></span></code></pre></div><p>Model confidence is not proof of existence. It describes a model’s judgment under particular inputs and assumptions. It does not replace provenance or verification.</p>
<h2 id="a-checklist-for-entity-design-in-ai-systems">A checklist for entity design in AI systems</h2>
<ol>
<li>Which entity types does the system recognize, and why?</li>
<li>Are mentions, names, classes, entities, identifiers, and records kept separate?</li>
<li>What establishes identity for each entity type?</li>
<li>How are aliases, namesakes, renaming, and duplicate records handled?</li>
<li>Do attributes and relations carry time and provenance?</li>
<li>Are events and changing states being flattened into misleading static fields?</li>
<li>Are extraction, linking, resolution, and real-world verification separate stages?</li>
<li>Can the system distinguish fictional, planned, hypothetical, and actual entities?</li>
<li>What happens to historical claims when entities merge, split, or change type?</li>
<li>Before acting, how does the system verify identity, current state, and permission?</li>
</ol>
<p>An entity-rich system can still be unreliable. Without identity criteria, provenance, temporal state, and authorization, it merely attaches confident-looking labels to uncertain referents.</p>
<h2 id="entities-connect-language-to-action">Entities connect language to action</h2>
<p>Entities form an interface between language, knowledge, and operations:</p>
<div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">objects, events, and states in a domain
</span></span><span class="line"><span class="cl">                ↓
</span></span><span class="line"><span class="cl">names and descriptions in language
</span></span><span class="line"><span class="cl">                ↓
</span></span><span class="line"><span class="cl">entity, attribute, and relation recognition
</span></span><span class="line"><span class="cl">                ↓
</span></span><span class="line"><span class="cl">links to records and external evidence
</span></span><span class="line"><span class="cl">                ↓
</span></span><span class="line"><span class="cl">interpretation of needs and intentions
</span></span><span class="line"><span class="cl">                ↓
</span></span><span class="line"><span class="cl">authorized action and recorded outcomes
</span></span></code></pre></div><p>An entity answers, “Which particular thing are we talking about?” An attribute answers, “What is it like?” A relation answers, “How is it connected?” An event answers, “What happened?” An intention answers, “What outcome is an agent trying to bring about?”</p>
<p>The most serious entity error in AI is not failing to label a noun. It is treating an ambiguous expression as though it already named one verified, current, and actionable object.</p>
<h2 id="references">References</h2>
<ul>
<li><a href="https://www.ahdictionary.com/word/search.html?q=entity">American Heritage Dictionary: entity</a></li>
<li><a href="https://plato.stanford.edu/entries/object/">Stanford Encyclopedia of Philosophy: Object</a></li>
<li><a href="https://plato.stanford.edu/entries/substance/">Stanford Encyclopedia of Philosophy: Substance</a></li>
<li><a href="https://plato.stanford.edu/entries/logic-ontology/">Stanford Encyclopedia of Philosophy: Logic and Ontology</a></li>
<li><a href="https://spacy.io/api/entityrecognizer/">spaCy: EntityRecognizer</a></li>
<li><a href="https://spacy.io/usage/linguistic-features#named-entities">spaCy: Linguistic Features—Named Entity Recognition</a></li>
<li><a href="https://www.w3.org/TR/rdf11-concepts/">W3C: RDF 1.1 Concepts and Abstract Syntax</a></li>
<li><a href="https://www.w3.org/TR/owl2-primer/">W3C: OWL 2 Web Ontology Language Primer</a></li>
</ul>
]]></content:encoded></item><item><title>Words, Concepts, and Objects: Reference and Reasoning</title><link>https://moonment.net/en/notes/words-concepts-and-objects/</link><pubDate>Tue, 15 Sep 2026 00:31:24 +0800</pubDate><dc:creator>Moon</dc:creator><guid>https://moonment.net/en/notes/words-concepts-and-objects/</guid><description>A practical distinction among parts of speech, semantic content, ontological categories, and the roles concepts play in reasoning.</description><content:encoded><![CDATA[<p>This essay examines the form of an expression, its conceptual content, the kind of thing it concerns, and the work it does in an argument. <a href="/en/notes/what-is-a-concept/">Concepts</a> develops the question of formation and boundaries; <a href="/en/notes/conceptual-and-logical-thinking/">Conceptual and Logical Thinking</a> follows these distinctions into reasoning.</p>
<h2 id="a-word-is-not-a-concept">A Word Is Not a Concept</h2>
<p>A word is a unit of language. A concept is something used in categorization, thought, inference, memory, learning, and decision-making.</p>
<p>The English word <em>water</em> is not identical to the concept of water. The concept includes ways of identifying water, expectations about its behavior, relations to other substances, and inferences that can be drawn about it. The same concept can be expressed in different languages, while a single word can express different concepts in different contexts.</p>
<p>A dictionary is therefore a starting point rather than a complete theory. It records established senses and patterns of use. Conceptual analysis must also ask what is being represented, how the representation is structured, and what work it performs in reasoning.</p>
<p>Philosophy offers no single accepted account of what concepts themselves are. Major approaches treat them as mental representations, cognitive abilities, or abstract objects. <a href="https://plato.stanford.edu/entries/concepts/">Stanford Encyclopedia of Philosophy: Concepts</a></p>
<h2 id="parts-of-speech-are-grammatical-categories">Parts of Speech Are Grammatical Categories</h2>
<p>Nouns, verbs, and adjectives describe how expressions function grammatically.</p>
<ul>
<li>Nouns commonly name or refer to people, objects, events, states, and abstractions.</li>
<li>Verbs commonly express actions, occurrences, changes, and continuing processes.</li>
<li>Adjectives commonly attribute properties, conditions, degrees, or evaluations.</li>
</ul>
<p>These patterns do not create a one-to-one map between grammar and reality.</p>
<p><em>Death</em> is a noun that can refer to an event. <em>Run</em> can be a verb naming an activity or a noun naming an instance, route, or sequence. <em>Red</em> can be an adjective attributing a color or a noun referring to the color itself. <em>Choice</em> is a noun derived from action language.</p>
<p>Grammar tells us how an expression is used in a sentence. It does not by itself settle what kind of entity, occurrence, or structure the expression is about.</p>
<h2 id="what-kinds-of-things-can-concepts-represent">What Kinds of Things Can Concepts Represent?</h2>
<h3 id="objects-and-entities">Objects and Entities</h3>
<p>Objects are typically treated as things that exist and retain some identity across change: a person, a tree, a phone, or a building.</p>
<p>Not every entity is a natural physical object. A corporation is a social and legal entity constituted by rules, roles, records, assets, and relationships.</p>
<h3 id="events">Events</h3>
<p>Events happen or take place: an arrival, an election, an explosion, a birth, or a death.</p>
<p>Philosophers often contrast objects, which exist, with events, which occur. The contrast is useful but disputed. Objects and events also differ in how they occupy space and time and in how they are identified. <a href="https://plato.stanford.edu/entries/events/">Stanford Encyclopedia of Philosophy: Events</a></p>
<h3 id="actions">Actions</h3>
<p>Actions are things agents do: promise, refuse, write, choose, repair, or work.</p>
<p>An action is not merely a bodily movement. Describing something as an action often introduces questions about intention, control, knowledge, ability, and responsibility. A movement that happens to a person and an action performed by that person may look similar while differing in agency.</p>
<h3 id="processes">Processes</h3>
<p>Processes unfold over time: learning, aging, erosion, cognition, and economic development.</p>
<p>A process may contain many events without having one natural endpoint. Learning is an extended process; passing a particular examination is an event within a longer history.</p>
<h3 id="states">States</h3>
<p>States obtain or persist for a period: knowing an answer, being unemployed, remaining stable, or feeling anxious.</p>
<p>A state description does not by itself explain its cause, permanence, or value. Calling someone anxious identifies a condition; it does not establish why the condition arose or whether it defines the person.</p>
<h3 id="properties">Properties</h3>
<p>Properties are attributed to objects, actions, and states: red, rigid, fragile, free, fair, or positive.</p>
<p>Some properties have agreed measurement procedures. Others depend on interpretive or normative standards. Length and fairness can both be predicated of something, but evidence for each is assessed differently.</p>
<h3 id="relations">Relations</h3>
<p>Relations connect two or more terms: resemblance, causation, ownership, kinship, dependence, rights, and obligations.</p>
<p>Many concepts that sound like self-contained qualities are partly relational. Significance, for example, often involves a relation among an event, an interpreter, a context, and a set of concerns.</p>
<h3 id="quantities-scales-and-models">Quantities, Scales, and Models</h3>
<p>Time, probability, price, risk, and efficiency do more than label a thing. They provide ways to order, compare, measure, or infer.</p>
<p>Their everyday uses may differ from their roles in a formal discipline. Saying that an outcome is “very likely” is not yet the same as assigning a probability under a specified model.</p>
<h3 id="institutions-rules-and-norms">Institutions, Rules, and Norms</h3>
<p>Money, offices, laws, promises, responsibilities, and justice depend on shared practices, constitutive rules, or normative judgment.</p>
<p>A banknote is a physical object, but its purchasing power cannot be explained by its physical composition alone. Institutional concepts connect material objects with recognized rules and social powers.</p>
<h3 id="abstract-objects">Abstract Objects</h3>
<p>Numbers, sets, propositions, possibilities, and perhaps concepts themselves are common candidates for abstract objects. They do not occupy ordinary physical space, yet they appear indispensable to mathematics and reasoning.</p>
<p>Whether abstract objects exist independently and how human beings could know them remain major philosophical disputes. <a href="https://plato.stanford.edu/entries/abstract-objects/">Stanford Encyclopedia of Philosophy: Abstract Objects</a></p>
<h2 id="events-processes-achievements-and-states">Events, Processes, Achievements, and States</h2>
<p>Language also distinguishes different temporal structures.</p>
<table>
  <thead>
      <tr>
          <th>Category</th>
          <th>Structure</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Activity</td>
          <td>continues without a built-in endpoint</td>
          <td>walking, thinking</td>
      </tr>
      <tr>
          <td>Accomplishment</td>
          <td>unfolds toward a completion</td>
          <td>writing a report</td>
      </tr>
      <tr>
          <td>Achievement</td>
          <td>culminates at a boundary</td>
          <td>reaching the summit</td>
      </tr>
      <tr>
          <td>State</td>
          <td>holds over time without unfolding toward a result</td>
          <td>knowing the route</td>
      </tr>
  </tbody>
</table>
<p>These distinctions matter because grammar can hide them. “She is writing the report” describes an incomplete process. “She has written the report” presents the completion. “She knows the answer” describes a state rather than an achievement now in progress.</p>
<p>The metaphysics of events and the linguistic study of aspect use related distinctions, although there is no universally accepted inventory of categories.</p>
<h2 id="concepts-also-perform-roles-in-reasoning">Concepts Also Perform Roles in Reasoning</h2>
<p>What a concept represents is only one question. A concept may also perform different tasks in an argument.</p>
<table>
  <thead>
      <tr>
          <th>Role</th>
          <th>Question</th>
          <th>Example</th>
      </tr>
  </thead>
  <tbody>
      <tr>
          <td>Description</td>
          <td>What happened?</td>
          <td>The team stopped the project.</td>
      </tr>
      <tr>
          <td>Classification</td>
          <td>What kind of case is this?</td>
          <td>This is a tactical decision.</td>
      </tr>
      <tr>
          <td>Explanation</td>
          <td>Why did it happen?</td>
          <td>Repeated interruption reduced attention.</td>
      </tr>
      <tr>
          <td>Prediction</td>
          <td>What is likely to follow?</td>
          <td>Higher exposure increases risk.</td>
      </tr>
      <tr>
          <td>Evaluation</td>
          <td>Is it good, bad, or important?</td>
          <td>The rule is unfair.</td>
      </tr>
      <tr>
          <td>Norm</td>
          <td>What should be done?</td>
          <td>Rights should be respected.</td>
      </tr>
      <tr>
          <td>Action guidance</td>
          <td>What do we do now?</td>
          <td>Stop investing and revise the goal.</td>
      </tr>
  </tbody>
</table>
<p>The same term can move among these roles.</p>
<p>Calling a mood <em>positive</em> may describe affect. Calling an employee’s attitude <em>positive</em> may evaluate conduct. Saying that someone <em>should be positive</em> adds a norm. A conversation can move across all three without marking the transition, turning an observation into a moral demand.</p>
<p>Similar errors occur with facts. A fact is a state of affairs that obtains. A causal explanation is a claim about why it obtains. A recommendation requires further premises about goals and values. Facts constrain recommendations, but they do not generate a complete practical conclusion on their own.</p>
<h2 id="why-ordinary-sentences-hide-multiple-concepts">Why Ordinary Sentences Hide Multiple Concepts</h2>
<p>Natural language compresses several layers of thought.</p>
<p>Consider the sentence:</p>
<blockquote>
<p>The plan failed, so the strategy was wrong.</p>
</blockquote>
<p>It contains at least four elements:</p>
<ul>
<li><em>plan</em>: an arrangement of intended actions;</li>
<li><em>failed</em>: an event description combined with a standard of success;</li>
<li><em>strategy</em>: a system of goals, diagnosis, choices, resources, and trade-offs;</li>
<li><em>so</em>: a claimed inferential connection.</li>
</ul>
<p>One failed plan may result from execution, timing, or chance. It does not by itself establish that the strategic diagnosis was false. The concepts must be separated before the inference can be tested.</p>
<p>Conceptual analysis therefore does more than define isolated nouns. It reveals compressed relations, shifting senses, and missing premises.</p>
<h2 id="a-three-pass-method-for-conceptual-analysis">A Three-Pass Method for Conceptual Analysis</h2>
<h3 id="1-identify-the-linguistic-form">1. Identify the Linguistic Form</h3>
<p>Is the expression functioning as a noun, verb, adjective, or complete proposition? Has an action or property been nominalized and treated as a thing?</p>
<h3 id="2-identify-the-represented-category">2. Identify the Represented Category</h3>
<p>Does it concern an object, event, action, process, state, property, relation, quantity, institution, or norm? Are different speakers referring to the same category?</p>
<h3 id="3-identify-the-inferential-role">3. Identify the Inferential Role</h3>
<p>Is the expression describing, classifying, explaining, predicting, evaluating, prescribing, or guiding action? Has the argument moved from one role to another without an explicit premise?</p>
<p>After these passes, further research can address etymology, historical change, disciplinary definitions, evidence, philosophical disputes, and practical limits.</p>
<h2 id="conclusion">Conclusion</h2>
<p>Concepts do not merely stand for “things,” and nouns do not map neatly onto objects. Thought concerns what exists, what happens, what agents do, what persists, what properties and relations obtain, and what rules or values should guide action.</p>
<p>Part of speech identifies a grammatical role. Ontological category identifies the kind of reality under discussion. Inferential role identifies what an expression is doing in an argument.</p>
<p>Keeping those three levels separate is a practical first step from word definition to conceptual analysis and from conceptual analysis to sound reasoning.</p>
]]></content:encoded></item></channel></rss>