Model

4 pages filed under Inference › model. A term is a word of the business with its definition, its aliases and the words it relates to.

TermaliasesFirst lineLinks
EntitynodeA node of the model: an instance of a type of the profile. An entity is nothing more than a keyword that owns a file of its name; a keyword page is what an entity becomes when nobody wrote that file.
Inferenceinference block, inference chainThe part of the pipeline that turns occurrences into links, keyword pages and twin resources, and the inference: block of the configuration that tunes it: glossary_sources, stopwords, short_terms and type_prefixes for the dictionary; cross_source_links for links across sources; ngrams and candidate_score for the candidate expressions; keyword_pages for the publication threshold; neighbours for the bounded neighbourhood; duplicates for the reconciliation of twin resources. Inference reads the model and the profile and nothing else, so two builds infer the same links.
Modelcanonical model, model.jsonThe result of a build: every entity, every link with its provenance, every finding, the term candidates and the neighbourhoods, serialised to a single model.json file in canonical order. Two builds on the same sources produce the same file byte for byte. The site is rendered from it without reading the sources again.
Querymodel queryA reading of the model from the command line, without the site: concordance query resolves an expression the way the recognition reads a note, then prints what the model knows about it, where it is used, what it is linked to and the decisions that touched it, or answers a question of the whole corpus, in a compact text made for a person at a terminal or for the context of an agent, every fact with its file and line. The answer is as fresh as the last build, and says so.

4 model of 4 — pagination by twenty. The Links column counts the related pages, which brings the most central model of the journey to the top.