Terminology
Use this page when a label or graph term is new to you. yggy uses one term for each concept throughout this guide.
| Term | Meaning | Example |
|---|---|---|
| Organization | The top-level account for members, projects, billing, data sources, and security settings. | Acme GmbH owns the Supplier research project. |
| Project | A workspace that limits access to documents, graph data, Review, and Chat. | Upload Q4-report.pdf to Supplier research, not to every project in the organization. |
| Document | A file or imported source record that yggy processes. | A PDF, spreadsheet, image, or selected cloud-drive file. |
| Extraction | The process that reads a document and creates graph data from it. | A completed extraction creates entities and triples from Q4-report.pdf. |
| Structured (SGSE) | Extraction that maps repeating source fields through a saved mapping. | A suppliers.csv file, or a parts table inside a PDF. |
| Text extraction | Extraction that reads free-form prose. | A cover letter or a procedure chapter. |
| Mixed | A document whose extract used both structured and text paths. | A service manual with a parts table and inspection steps. |
| Entity | A person, place, organization, product, event, or other thing in the graph. | Atlas GmbH is an entity with type organization. |
| Entity type | The class that states what an entity is. | organization, person, or product. |
| Triple | One graph statement with a subject, predicate, and object. The UI can also call it a relation when it connects two entities. | (Atlas GmbH, located_in, Berlin). |
| Predicate | The named meaning of a triple’s connection. | located_in in (Atlas GmbH, located_in, Berlin). |
| Literal property | A typed value attached to an entity instead of another entity. The UI and ontology can also call this a data property. | (Case 1093, occurred_at, "2026-07-29T08:30:00Z"). |
| Triple qualifier | Context that belongs to one exact triple, also called triple metadata. | currency: EUR and unit: kg qualify (Tomatoes, has_purchase_price, Measurement "5.30"). |
| Knowledge graph | The entities, triples, literal properties, and source links that yggy stores. | Follow supplies from a supplier to the products it supplies. |
| Ontology | The vocabulary that defines valid entity types, predicates, and literal properties. | It states that located_in connects an entity to a location. |
| Mapping | The rules that turn fields in structured source data into graph facts and source attributes. | Map the CSV field opened_at to the occurred_at literal property. |
| Source attribute | A source field that yggy keeps without giving it a shared graph meaning. | Keep archive_batch: A7 with the source record. |
| Source evidence | The document, source text, or source record linked to an extracted fact. | Open a triple to inspect the sentence that supports it. |
| Review item | An uncertain entity merge, a contradiction, or another graph decision that needs a person. Confident same-name merges can complete without a click. | Keep two Atlas entities separate when one is a company and one is a product. |
| Contradiction | Two facts about the same subject and relation that cannot both hold at the same time. Review asks a person which one stays current. | One source places Atlas GmbH in Berlin, another in Munich. |
| Workflow | One background document-processing run and its status. | Retry a failed extraction workflow after you fix the source file. |
| Data source | An external service that yggy can connect to. Each provider supports its own actions. | For example Google Drive, OneDrive / SharePoint, or Linear when that type is configured. |
| Connection | An OAuth authorization for an AI assistant, or an API token for REST. | Revoke a former laptop’s MCP client in Developers → Apps. |
| MCP | Model Context Protocol, the protocol that exposes yggy tools to compatible AI clients. | Connect Claude Code to search the graph. |