Which statement best describes Object Type vs Object?

• A. An Object Type is the schema definition that applies only to datasets and has no relation to properties.
• B. An Object Type is the schema definition of a real-world entity that defines properties, types, primary key, and backing datasets; An Object is a single instance of that type.
• C. An Object is the schema definition.
• D. Object Type and Object are interchangeable terms.

Answer: (B)

In Palantir Foundry, an Object Type is the blueprint for a real-world entity, defining its properties, the data types of those properties, a primary key to identify unique instances, and which backing datasets hold the data. An Object is a single instance of that blueprint—one specific real-world entity described by that type, with values for its properties sourced from the backing datasets. For example, you might have an Object Type for a Customer with properties like customer_id (the primary key), name, email, and address, and backing datasets from CRM and Billing. A particular customer then becomes an Object, embodying those properties with actual data.

The other statements don’t fit because the Object Type is not limited to datasets and not unrelated to properties; it actually defines the structure and constraints for those properties and how data is stored across datasets. The Object is not the schema itself, but the concrete instance of that schema. And they aren’t interchangeable—the Object Type provides the blueprint, while an Object is a single realized entity.