Skip to content

2026-04-27-layered-ontology-model#126

Merged
n-gao merged 12 commits intoiclr-blogposts:mainfrom
minogame:main
Apr 7, 2026
Merged

2026-04-27-layered-ontology-model#126
n-gao merged 12 commits intoiclr-blogposts:mainfrom
minogame:main

Conversation

@minogame
Copy link
Copy Markdown
Contributor

@minogame minogame commented Dec 7, 2025

OpenReview Submission Thread

https://openreview.net/forum?id=Lykh7TS4Tu

Checklist before opening a PR

  • I am opening a pull request against the main branch of the 2026 repo.

  • My post and all associated references to it are all lowercase, i.e

      2026-04-27-Sample-Test.md               -> 2026-04-27-sample-test.md
      assets/img/2026-04-27-Sample-Test/ 	-> assets/img/2026-04-27-sample-test/
    
  • The title of my PR is exactly the name of my markdown file

    • i.e. _posts/2026-04-27-[submission-name].md would require a PR name 2026-04-27-[submission-name]
  • I have anonymized my post: my author's list is Anonymous, and there is no potential
    content which can reveal my/my collaborators identities.

  • My post matches the formatting requirements, including (but not limited to):

    • I have ONLY MODIFIED files in the following locations (failure to do so will result in
      your PR automatically being closed!):
      • a Markdown (or HTML) file in _posts/ with the format _posts/2026-04-27-[submission-name].md (or .html)
      • static image assets added to assets/img/2026-04-27-[submission-name]/
      • interactive HTML figures added to assets/html/2026-04-27-[submission-name]/
      • citations in a bibtex file in assets/bibliography/2026-04-27-[submission-name].bib
    • I have a short 2-3 sentence abstract in the description field of my front-matter
    • I have a table of contents, formatted using the toc field of my front-matter
    • My bibliography is correctly formatted, using a .bibtex file as per the sample post

Any other comments

Copilot AI review requested due to automatic review settings December 7, 2025 15:20
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR introduces a blog post proposing a five-layer ontological framework for understanding AI models, particularly Large Language Models. The framework distinguishes between the Noumenal, Conceptual, Instantiated, Reachable, and Observable models, and uses this structure to analyze philosophical questions about meaning and truth in AI systems.

  • Proposes a five-layer hierarchical ontology ($\mathcal{M}_N$, $\mathcal{M}_C$, $\mathcal{M}_I$, $\mathcal{M}_R$, $\mathcal{M}_O$) to decompose AI model concepts
  • Reconstructs philosophical thought experiments (Stochastic Chinese Room, Paradox of Two Poetics) through this framework
  • Analyzes the evolution of model conceptualizations from classical ML to foundation models

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.

File Description
_posts/2026-04-27-layered-ontology-model.md Main blog post introducing the five-layer ontological framework and philosophical analysis of AI models
assets/bibliography/2026-04-27-layered-ontology-model.bib Bibliography with 13 references including philosophical works (Kant, Searle, Frege) and AI/cognitive science papers

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread _posts/2026-04-27-layered-ontology-model.md Outdated
Comment thread _posts/2026-04-27-layered-ontology-model.md Outdated
Comment thread _posts/2026-04-27-layered-ontology-model.md Outdated
@busycalibrating busycalibrating added the accepted PR matches an accepted blog post label Mar 24, 2026
@n-gao n-gao merged commit 51a9837 into iclr-blogposts:main Apr 7, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

accepted PR matches an accepted blog post manual accept

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants