AI Entity Enrichment PlatformYour documents already describe a data model.

Schema generation groups the fields by the knowledge they call for, and gives each group an expert: here a literary expert for titles, genres, authors and series, and a publishing expert for publishers, prices and publication years. Fields are shared out one by one, not entity by entity: a book's title goes to one expert, its price to the other. A schema gets at most one expert for every six fields, so a small one is not split too finely.

At enrichment, each expert can become a call of its own, run in parallel: a model asked only about prices and publishers answers them more fully than one asked about everything at once.

Each expert then writes the description of its own fields, in its own vocabulary: which year a book's year is, in which currency and at which date its price is read. The experts write side by side, one call each. A description is the question a model answers for its field at enrichment, so a precise one is what makes two models, or two runs, fill the field alike.

For each entity type, schema generation picks the fields that identify one instance — a book's title, an author's name. Dante and Dan Brown each wrote an Inferno: a book is told apart by its title and its author together.

When semantic IDs are requested, each object that represents an entity gets an id field: the book, and each entity nested under it — author, series, publisher. The model never fills it: after each enrichment, it is resolved from the entity's identifying fields, so the same author written two ways keeps one identifier.

An object that only holds facts of its parent — here the book's year and price — gets none: no field in it identifies anything. Neither does a pairing, such as a book's volume number in its series: it is identified by the two entities it relates.

A text field can be marked multilingual: it then holds one value per requested language — a title, a genre or a country written in each of them, a name in each language's script. A year or a price stays a single value. Identity is read in the first language, so a translated title never creates a second book.

For each entity, one or several language models fill the schema from the attached documents and from their own knowledge. A field marked preserved is the exception: its value comes from your own system — a row id, an internal reference — and passes through the enrichment unchanged, so each enriched book goes back to the row it came from. Unmarked, the field is the model's to fill, and nothing keeps it from writing the ISBN it knows in place of your id.