Using the ontology below, an AI can retrieve the metric and customer–payment link to write SQL for “Which customers paid most?”
Customer, PaymentObjects: , ; is finite.
payment.customer_idSignature: .
payment.amountSignature: .
customer lifetime valueSignature: (total paid by each customer).
NVIDIA Auto Ontology instantiates its semantic ontology as a graph, constructed and queried through Python. However, other applications may require different substrates.
| Representation | How the ontology is expressed | Examples |
|---|---|---|
| Typed mathematical formalisms | Types, definitions, operation signatures and laws governing the operations. | Math-in-the-Middle (slide 14); mathlib, the library of the proof assistant Lean. |
| Logic-based ontology languages | Classes, individuals and relations constrained by logical axioms. For example, OWL's SubClassOf(:Bond :TradableDebtInstrument) states that every bond is a tradable debt instrument. |
FIBO (slide 48) and OntoPlan (slide 23), in OWL; SUMO, in SUO-KIF. |
| Graph | Typed nodes connected by named relations. RDF expresses links as subject–predicate–object triples. | NVIDIA Auto Ontology (slide 8); OntoPlan’s RDF world model (slide 23). |
| Annotations on models or data | Links from variables or objects to the terms of an ontology. | SemGen’s biological models (slide 14); NVIDIA’s scene objects (slide 13). |
The scope remains open; WG1 could investigate these overlapping candidates.
The domains can overlap; ontologies for the same domain can use different substrates.
Define the scope of semantic ontologies for computational economics.
| Use | Published finding | Source |
|---|---|---|
| AI training data (NVIDIA) | NVIDIA’s Omniverse simulation platform labels scene objects with identifiers from Wikidata, a public knowledge base, through the semantic-label schema of the OpenUSD scene format. The labels give AI training data its object categories. | NVIDIA specification OpenUSD schema |
| Robot planning (OntoPlan) | OntoPlan achieved 89% task success, against 27% for SayPlan, a comparison system given the same scene facts. | Nam et al. (2026) NeurIPS (accepted) |
| Robot experience (KnowRob) | The KnowRob knowledge system used an ontology to retrieve grasp poses and forces from recorded robot actions. | Beetz et al. (2018) ICRA |
| AI program translation | Training a code model to emit symbolic expressions for numeric constants, which a rule-based interpreter converts to IEEE-754 values, raised the share of C functions whose generated assembly passed input–output tests from 3.8% to 92.6% on 21,104 functions. | Zhang et al. (2024) EMNLP Findings |
| AI theorem proving (LeanDojo) | Retrieving existing Lean library results raised proof success from 23.2% to 26.3% on 2,000 theorems requiring results not used in training. | Yang et al. (2023) NeurIPS |
| Numerical checking (SMT-LIB) | SMT-LIB, a standard input language for automated reasoners, defines floating-point types, operations and rounding modes, so that a reasoner can check a floating-point computation. | Brain et al. (2015) IEEE ARITH |
| Use | Published finding | Source |
|---|---|---|
| Factory planning | Software converted an existing factory ontology and machine-operation descriptions into 267 planning actions in about 15 seconds. | Malburg et al. (2023) Eng. Appl. AI |
| Assembly planning (Ford) | Ford’s deployed assembly-planning AI used an ontology to interpret vehicle-build instructions and to share that knowledge with other applications. | Rychtyckyj et al. (2016) IAAI |
| Materials data (MDS-Onto) | MDS-Onto defines terms for X-ray and solar-energy measurements, which software uses to generate data templates and machine-readable datasets. | Rajamohan et al. (2025) Scientific Data |
| Model composition (SemGen) | SemGen used ontology terms to match variables by biological meaning and combine models in different formats. | Neal et al. (2019) Bioinformatics |
| Arterial-model assembly | SemGen merged semantically annotated bond-graph modules, whose junction laws conserve mass and energy, into an 86-vessel arterial model from three templates. | Shahidi et al. (2021) PLOS Comput. Biol. |
| Biological inference (GO-CAM) | Gene Ontology uses logical rules to infer additional labels for gene functions and distributes them in standard releases. | Thomas et al. (2019) Nature Genetics |
| Mathematical software | A shared mathematical ontology, Math-in-the-Middle, let three computer-algebra systems, SageMath, GAP and Singular, each perform a step of one polynomial calculation. | Kohlhase et al. (2017) MACIS |

What must a reader know to understand the joke?
Set-theoretic semantics. A function from each word to a subset of a set of individuals gives the denotations , the sets of things each word applies to. Such a mapping, Guizzardi and Guarino (2024) say, "would not do Maurice here any good".
Ontology. The kinds and relations the words are about form a separate system, which the paper states as three facts. Ham, bacon and sausage are food products constituted by pork. Pork comes from a pig. Maurice is a pig.
The joke here arises from the system of kinds and relations, not from the set-theoretic semantics.
Above the line stand the words, the written form. Below it stand the kinds, individuals and relations, the domain of meaning. The dashed arrows are Υ, which assigns each word its meaning. The solid arrows state relations between kinds and do not identify Maurice as the source of any particular ham.
Semantics. A set-theoretic semantics maps each word to a subset of a set of individuals, , and nothing more.
Ontology. The ontology is a separate system of kinds, individuals and relations, written as typed symbols.
| The pigs | The buffer-stock model | |
|---|---|---|
| Written form | in the Bellman equation | |
| Semantics, into a set | , some operator | |
| Left open | foods for pigs, or foods from pigs | which variable chooses and which averages over, the space of , the law and timing of |
| Ontology, typed statements | , , | , with law , |
| False agreement | two pigs agree that the words name foods, one meaning foods for pigs and the other foods from pigs | two readers accept the Bellman equation and disagree on the timing of the response to a shock (slide 31) |
Nam et al. (2026), accepted at NeurIPS 2026.
OntoPlan combines a language model with planning software for indoor robot tasks in symbolic simulation. Its ontology defines object types, relations and inference rules, while a matching action model specifies what each action changes.
Illustrative task. Move a toothbrush from a cabinet to another room.
| Model component | Toothbrush example |
|---|---|
| Objects and types | The toothbrush and the cabinet have type Artifact (physical object), while the room has type Space. |
| Relation | The toothbrush is inside the cabinet. |
| Action effect | After pickup, the toothbrush is held by the robot’s hand and is no longer inside the cabinet. |
| Inference rule | A carried object is in the same room as the robot. |
Space as the set of spaces and carries as the relation between a robot and the objects it carries.The same study compared three AI planning systems on 150 simulated robot tasks. All used GPT-4o, the same scene facts and the same 16 primitive actions, and their plans were checked against the same preconditions and effects.
| System | Success rate |
|---|---|
| OntoPlan | 88.7% (133/150) |
| SayPlan | 27% |
| DELTA | 13% |
OntoPlan retrieves the relevant facts, constructs the plan and records the consequences of each action. DELTA also had formal action rules and plan-constructing software, which means that formal rules alone do not account for OntoPlan's gain.
Within OntoPlan, the authors compared selecting relevant facts with supplying all scene facts as text.
| Facts supplied to AI | Growth in the largest input |
|---|---|
| Relevant facts selected from the ontology | 1.06× |
| All scene facts supplied as text | 8.13× |
Task success was 89% with selected facts and 87% with all facts, a difference that was not statistically significant.
This case shows that a machine reading a mathematical description of a model misses part of its meaning. Consider an excerpt from a written statement of the buffer-stock saving model:
Each period the household arrives with assets , receives income and earns the gross return on those assets, where is the gross interest factor. Market resources are then . Income is i.i.d. with . The household chooses consumption , leaving , to solve the Bellman equation
The right-hand side defines an operator with , which sends the function to the function , backward from a given terminal value over a finite horizon.
Implicit context. Economists write code that implements from their own understanding of dynamic programming, which the statement leaves implicit.
By itself, machine reading the statement does not give enough information to build .
The difficulty is not one of parsing. A machine parses the statement, that is, splits it by grammar rules alone into a parse tree of its symbols, whereas the tree, with no structure added to its symbols, records nothing of the model's meaning. See the appendix on parse trees.
A semantic ontology makes that implicit understanding explicit.
The tables on this slide and the next two list some of the meaning that a parse of the buffer-stock statement misses.
| Missing meaning | In the buffer-stock statement |
|---|---|
| Variable bindings | The maximisation binds , while the expectation binds . The left-hand side binds by defining as a function of , which leaves free inside the right-hand side. |
| Parameters | The paper defines , , and the law of elsewhere, in no fixed place. Of these, only and are numbers, while is a function and the law is a probability measure, a difference the statement does not show. |
| Symbol types | The value function maps to , with a point of its domain. The tree records both symbols but not that evaluates a function at a point of a particular type. |
| An equation between functions | For each the Bellman equation equates two numbers. Over all it is one equation between functions, , in which maps to . |
| Missing meaning | In the buffer-stock statement |
|---|---|
| Whether a symbol is a variable, a function, or a random variable | The symbol , defined by , is i) the path of one household's resources, ii) the function composed inside the operator, and iii) the random variable whose law is the cross-sectional distribution. A paper writes one symbol for all three meanings, whereas code must represent them as three objects of different types with different uses. |
| Shock law | The statement fixes . In the shorter form , denotes the mean of under one convention and the mean of under another. |
| Missing meaning | In the buffer-stock statement |
|---|---|
| Implications of timing stated in words | In a model with entry, beyond the excerpt of slide 27, the sentence "A policy shock raises entrants at date " is satisfied by two different models, because the shock may reach the cross-sectional distribution at or at , while nothing in the paper records which one the code computes. |
| What the household knows when it decides | If the return is random, persistent and drawn before the decision, the household's expectation of depends on whether it observes or only when it decides. |
Several readings. One well-formed statement admits two or more readings of its parse tree. The appendix gives examples of false agreement, in which two readers accept the same statement and compute different models.
Human readers. False agreement rarely arises when an economist reads the model. An economist has been taught that in is the point at which is evaluated, not a path of assets across a population.
Timing and information. Even so, the timing of events and what the household knows at each decision confuse economists themselves.
AI readers. When we rely on an AI's statistical reading of the text, we cannot be sure that it has read the model correctly, even when its reading appears correct most of the time.
Perches. A perch is one of the three information sets of the stage: arrival !arvl, decision !dcsn and continuation !cntn.
Fields. A field is a state or a value declared at a perch together with its set, as in m : ℝ₊₊ @ !dcsn. The role tags !ctrl and !vlu mark a chosen variable and a value.
Blocks. A block holds the equations between two perches: the transition with the shock, whose law line y ~ LogNormal(μ_y, σ_y) declares its distribution, the choice in the [id=policy] block, and the expectation.
!vlu marks a value. The marks [>] and [<] give the continuation and arrival values v≻ and v≺, whose spaces are 𝖵≻ and 𝖵≺, beside 𝖵 at the decision perch. The elaborator, the program that constructs those objects, refuses a line that the types do not admit and names the rule.| Line in the file | Under Υ it denotes |
|---|---|
V[>] : ℝ @ !vlu at the continuation perch |
, a function of savings, never a number |
the choice block [id=cntn_to_dcsn] with its [id=policy] block |
, the choice operator |
the expectation block [id=dcsn_to_arvl] |
, the expectation operator |
| A line that | The elaborator |
|---|---|
adds the shock outside its own expectation, V[<] = E_{y}(V) + y |
refuses it under shock-reintroduced, since is not known at arrival |
| lists a continuation value at the decision perch | refuses it under field-perch, since the value is a function of savings |
puts the mean of the shock in the transition, m = R*k + exp(μ_y + σ_y^2/2) |
accepts it, leaving the different model visible on that line |
writes a second β in the expectation block |
accepts it, leaving the second β visible on its own line |
| would impose a stationary closure | has no line for it, since V[>] comes from the next period or the terminal value |
elaborate_text of 13 October 2026.Dynare and other tools already turn model descriptions into computed results.
With a shared economic interpretation. The upper route states the interpretation separately. Υ maps the written model to a typed model object, ⟦file⟧, to which Ρ (rho) then attaches a numerical method.
Successful compilation or execution does not establish agreement with the intended economic model.
Shared definitions. Give the AI an ontology that specifies the economic objects, their units, timing and relations.
Links to code. Identify the variables and functions that implement each shared economic definition.
Checks on model agreement. Check declarations against the ontology, review the links to code, and test the numerical results.
QuantEcon’s community library asks each toolkit to implement a shared model and calibration with its own solution method, in a runnable tutorial.
| Part of a contribution | Buffer-stock example |
|---|---|
| Common economics | Equations, timing, shock laws, normalisation and calibration. |
| Implementation choices | Solution method, shock approximation, grids, interpolation and software version. |
| Comparison quantities | Consumption, target resources, marginal propensities to consume and the seven model conditions listed in the submission guide. |
| Published precedent | What was done |
|---|---|
| SemGen | Ontology annotations matched biological quantities across different model formats. |
| Math-in-the-Middle | Symbols from SageMath, GAP and Singular were mapped to shared mathematical definitions. |
| BioModels, a curated database of biological models | Curators annotated model entities and reproduced published simulations. |
Proposed for the library. Link each implementation’s variables and operations to agreed economic definitions. The links align the written terms. Interpreting those terms as economic objects is what Υ does.
In the buffer-stock description, target resources are the level of resources, measured relative to permanent income, at which expected next-period resources equal current resources.
| Points in the income-shock approximation, besides the zero-income point | Saved HARK estimate of target resources |
|---|---|
| 7 | 1.3910 |
| 21 | 1.3994 |
The same model and calibration give different numerical estimates when the shock approximation changes.
Proposed pilot. Start with the full buffer-stock description and the HARK contribution before adding a second toolkit.
Task. Ask an AI to identify comparable results and report differences in numerical settings.
Comparison. Compare the AI’s answers with and without semantic annotations, using the same complete model statement, equations, calibration and run information. Record correct matches, incorrect matches and cases requiring review.
Excludes. The ontology excludes three misreadings. A missing annotation may not be read as the absence of a function, under the open-world assumption, which treats an absent statement as unknown rather than false. A NOT qualifier, which records that a gene lacks a function, may not be read as an inconclusive result. A term may not be read by its name rather than by its definition and relations, since a label must be unique and a definition must always denote the same referents (principles 12 and 19 of the OBO Foundry, the body that sets the rules for biomedical ontologies).
For economics. A model's object is named by a term with a definition and relations, not by a variable name. The role tags !ctrl and !vlu and the law line of a stage file play that part, as the sboTerm of the Systems Biology Ontology does for a rate law in SBML, the exchange format for biochemical models.
Excludes. The ontology excludes a model confused with the system it models and a model variable confused with the physical quantity it stands for. The relation models joins a model to its system, while correspondsToQuantity pairs a variable with a quantity, as a declared domain excludes the deck's function on the wrong space (slide 55).
For economics. OntoCAPE is the nearest case to Project A because it is an ontology of models themselves. Model variables, equation systems and solution strategies are kinds in its modules (its sub-ontologies), so that a process model and its solver are distinct typed objects, as Υ and Ρ keep a model apart from its numerical method.
Excludes. The ontology excludes a quantity name read as any of several kinds, since a SWEET class fixes the kind by its definition and by its place among realms (SWEET's divisions of the Earth system), quantities and phenomena. The Climate and Forecast (CF) standard names, published as SKOS concepts (the W3C's format for agreed lists of terms) on the NERC vocabulary server, each linked to its canonical unit, settle the same question for a variable such as temp in a netCDF data file (a format for climate data). In the deck's terms this is the question of the shock law (slide 30) and of timing stated in words (slide 31).
For economics. The comparison paper of the special issue that Project A proposes needs a vocabulary of this kind: which object each team reports, a value or a marginal value function, on which state and under which timing, as in the comparison projects that den Haan, Judd and Juillard (2010, 2011) introduced.
Excludes. The ontology excludes an issuer read as the obligor (the party that owes the payments) of a bond and a notional amount read as a principal, since each is a defined class or property (OWL's word for a relation). The 2023 revision of the Swaps ontology separated the nominal from the notional amount, which its change note says "were confused". In the deck's terms these are a function on the wrong space (slide 55) and the shock law (slide 30).
For economics. FIBO is finance's own ontology, with the Bureau of Economic Analysis, the Bureau of Labor Statistics, the CFTC and the Office of Financial Research among its contributors. The 2026 rule under the Financial Data Transparency Act records it among the standards that commenters proposed. Project A's ontology names the objects of a model as FIBO names the parties and terms of a contract.
Excludes. The language excludes any reading of the axioms other than the one fixed by the Direct Semantics, OWL's official rule for what its statements mean, under which "the correct answer to any such question is predetermined by the formal semantics", whatever reasoner computes it (Primer §2). It also does not read a missing statement as false, and it does not assume that two names denote two individuals.
For economics. This is the three-part definition in full: classes, properties and individuals as typed symbols, an interpretation as the domain, and a map whose consistency (that the axioms do not contradict one another) and entailments (what follows from them) a reasoner decides. A stage file's Υ plays the part of the Direct Semantics, and the elaborator the part of the reasoner.
| Ontology | Written form | Domain of meaning | Map Υ | Checker |
|---|---|---|---|---|
| Gene Ontology | the GO terms, each by ID | kinds of molecular function, biological process and cellular component | the term in a GAF annotation | the ELK reasoner, on every pull request and push to master |
| OntoCAPE | OWL classes and relations in 62 modules | models, systems, materials and quantities | the axioms, models and hasModelVariable |
the RacerPro reasoner |
| SWEET and the CF names | OWL classes, and SKOS concepts for the CF names | Earth-science quantities, realms and phenomena | the class, or the standard name on a variable | any OWL tool; the CF checker against the standard-name table at cfconventions.org |
| FIBO | OWL classes and properties | contracts, instruments and parties | the class asserted of a record | a consistency check by Openllet or HermiT, whichever answers first |
| OWL 2 | classes, properties and individuals | an interpretation: a set with relations on it | the Direct Semantics | a reasoner: consistency and entailment |
| Part | In the Bellman-SYM stage file |
|---|---|
| Written form | the fields and the blocks, each with a type and a perch, and the declared law of the shock (slide 33) |
| Domain of meaning | state spaces, laws, value functions and the operators between them (slide 7) |
| Map Υ | the perch tags @ !arvl, @ !dcsn and @ !cntn, the role tags !ctrl and !vlu and the law line (slide 33), interpreted by Υ (upsilon), the checked interpretation of slide 53, as the objects of slide 7 |
| Checker | the elaborator (slide 34), which constructs the typed object or refuses the file, naming the rule the file breaks and the line; and the comparator, a program that compares two elaborated files up to renaming and reports, for each kind of item, agreement, difference or an undecided residue, the items it can neither match nor reject |
| Run on the file of slide 33 | The elaborator constructed the object from the file and refused the line E_{y}(V) + y, with y listed among the block's inputs, under shock-reintroduced.The comparator read the file and the documentation example, with b and w for k and m, as one object under that renaming. |
elaborate_text of bellman.factory.elaboration and compare of meaning_map_training.compare, 13 October 2026, on the stage file of slide 33 and on Bellman-SYM's documentation example (Stages §4).Parsing a written statement into a tree, as every compiler first does, shows what the statement leaves to context.
What the parser does. It splits v = u(c) + beta * w into a tree by grammar rules alone.
What the tree records. The tree records only which symbol is applied to which, node by node.
What the tree omits. The tree records nothing about what v, c or w are, which variable is bound where, or whether v is a function.
ast.parse("v = u(c) + beta * w").In the model, is not a number obtained by adding to . That sends a function to a function appears only once the binders, types and declarations on the right are attached to the tree by the dotted lines in the figure, which turn the tree into the semantic graph.
The paper's Bellman equation gives the date as its subscript rather than the variable it integrates. Because the tree specifies neither that variable nor the type of , each box below puts the paper's expression to the left of "read as" and a reading that the tree does not exclude to the right.
The shock leaves the expectation.
Since Jensen's inequality gives for concave , the first reading overstates the continuation value. Because it replaces the income risk by its mean, it also removes the precautionary motive, the saving held against that risk (Kimball 1990). The second reading treats as known before it is drawn.
The expectation moved through the maximisation.
Since , the reading on the right overstates the value and lets consumption respond to income that has not yet been drawn.
A number where a function belongs.
The backward step then returns one number and one consumption , although needs at every . Under this reading the reader has simulated a path where the model asked for a function.
A function on the wrong space.
The borrowing limit acts at , a point at which a function of resources is not defined, so that the two functions have different domains. A reading that confuses them puts the boundary at a point where the constraint does not act.
The discount and the expectation applied by both steps once is split.
Since the Bellman equation writes and once each, an implementation that splits into the choice and the expectation must decide which step applies and which applies . An implementation that applies and in each of the two steps makes the household discount at and draw income twice.
Dated value functions read as one stationary function.
A stationarity condition that the statement never makes replaces the backward recursion from a terminal value. Once the terminal value has disappeared from the problem, the last period's consumption is chosen as if another period followed.
Autoformalization. The AI translates the paper into the written form, which the checker accepts or refuses (Wu et al. 2022, where the checker decided syntactic correctness and people judged faithfulness; AlphaProof, Hubert et al. 2026, which learned by reinforcement with Lean's kernel, the core program that checks each proof step, as the verifier).
Refuse and repair. The checker's refusal, with its rule named, is the AI's next prompt, as the error message of a proof assistant (a program that checks proofs) is in Baldur, a proof-repair system (First et al. 2023). The elaborator's rules shock-reintroduced and field-perch are messages of this kind.
Constrained generation. The AI's output is restricted, as the AI produces each word of its output, to the grammar of the written form, so that only its meaning remains to be checked (Poesia et al. 2022; Geng et al. 2023).
Compute, then answer. From the accepted file the ontology's programs compute Υ's object and Ρ's numbers (or, for a proof, the kernel checks it), so that the AI's answer to the user is built from that output rather than from its own guess.
Round trip. A second program writes the accepted object back into prose for a judge, a program or a second AI, to compare with the paper (Li et al. 2024), or regenerates the object for comparison with the original (Allamanis et al. 2024). Matsya, the project's assistant service, runs the first loop with the elaborator and two judges and the second with its comparator.
Retrieval over a knowledge graph. The AI answers from a graph of entities and relations rather than from passages alone (surveyed in Pan et al. 2024; GraphRAG, Edge et al. 2024, which answers from summaries of entity clusters). Matsya retrieves passages of the project's documents with their sections, links and tags, and reads the typed object itself when a question names a stage file.
Training on generated pairs. The ontology's programs generate pairs of a file and its prose, or the comparator labels two files as one object or as two, so that a model can be trained on the pairs. AlphaProof's roughly one million natural-language problems, auto-formalised into about 80 million formal statements, are the largest instance. The project's comparator module, meaning_map_training.compare, labels such pairs, while the package's own training revises Matsya's instruction texts and settings against the round trip, with the language models' weights fixed.
What separates the two groups. In the five uses of the previous slide the checker, not the AI, decides what the file means, which makes the AI's reading inspectable. In these two the AI's reading improves but stays statistical, which is why they do not replace the checker.
meaning_map_training.compare: bellman-ddsl (internal).1. Objects and rounding. We use finite FP32 (IEEE 754 single-precision) values . For the calculations below, rounds a real number to nearest FP32, with ties to even.
2. Interpretation Υ. Fused multiply-add rounds once; separate multiplication and addition round twice.
3. NVIDIA's example. Set and .
The input types agree, but the rounding rules and results differ.
slide 1 · Semantic ontologies
slide 2 · Communicating with AI
slide 3 · Main concepts (section)
slide 4 · Definitions (subsection)
slide 5 · Meaning as a relation to a domain
slide 6 · Semantic ontology
slide 7 · Three parts to a semantic ontology
slide 8 · NVIDIA Auto Ontology: customers and payments
slide 9 · Ways to represent and use an ontology
slide 10 · Scope (subsection)
slide 11 · Possible semantic ontologies for economics
slide 12 · WG1's task
slide 13 · Semantic ontologies and formal methods in AI
slide 14 · Evidence – shared models and operational uses
slide 15 · Semantic Ontologies in Action (divider)
slide 16 · Pig goes to the library (divider)
slide 17 · What the pig learned in the library
slide 18 · The set-theoretic semantics is not enough
slide 19 · When Maurice learns the ontology
slide 20 · Semantics and ontology
slide 21 · OntoPlan – robot task planning (divider)
slide 22 · Motivating example from robotics
slide 23 · OntoPlan’s ontology defines object types and rules
slide 24 · Ontology-based planning achieved 89% task success
slide 25 · OntoPlan kept AI inputs small as scenes grew
slide 26 · Project Bellman (divider)
slide 27 · A mathematical description of a model
slide 28 · Context
slide 29 · The missing-meaning problem
slide 30 · The missing-meaning problem
slide 31 · The missing-meaning problem
slide 32 · Multiple possible parsed meanings
slide 33 · The ontology – one stage of the buffer-stock model
slide 34 · What the ontology checks and makes explicit
slide 35 · Current modelling tools and AI (divider)
slide 36 · What Dynare and other modelling tools do
slide 37 · What AI needs beyond code compilation
slide 38 · The community library (divider)
slide 39 · One model, several numerical implementations
slide 40 · Link toolkit variables to shared model definitions
slide 41 · Two estimates of one defined quantity
slide 42 · Use the library to test WG1’s common definitions
slide 43 · Appendix (divider)
slide 44 · Further examples (divider)
slide 45 · Biology – the Gene Ontology
slide 46 · Engineering – OntoCAPE, the ontology for chemical process engineering
slide 47 · Earth science – the SWEET ontologies
slide 48 · Finance – FIBO, the Financial Industry Business Ontology
slide 49 · Knowledge representation – OWL 2, the language ontologies are written in
slide 50 · The five reference ontologies against the three parts of a semantic ontology
slide 51 · The stage file against the same three parts
slide 52 · The parse tree of a written statement
slide 53 · From the parse tree to the semantic graph
slide 54 · What the expectation integrates
slide 55 · A number for a function, and a function on the wrong space
slide 56 · The discount and the expectation applied twice, and the recursion as a fixed point
slide 57 · How an AI works with a semantic ontology (divider)
slide 58 · The AI writes against the ontology
slide 59 · The AI reads from the ontology
slide 60 · NVIDIA FP32: fused multiply-add