JSON LD with ID only parse as "embeded item"

Question

Im using JSON-LD as part of one of my website... And i found there too many data, that point to "myself" or "the company i work for"... so i decided to use partial item definition and @id attribute to reduce redundancy of these definitions.

Well there is an issue: If i use for example my company to relate myself to my company, google will fetch this data and view it as separate card of information which is linked for example to my working company, while the website has nothing to do with that company, it's only me as person which that card relate to...

to be honest i like it when it detect me, both, separately as a person, and merged as a member of website definition, but i dislike it about the organization, and i'm looking for a member that turn this feature off is available...

Here i like That google Know this element as a Person and as a part of WebSite

<script type="application/ld+json">
{
    "@context": "http://schema.org",
    "@type": "Person",
    "@id":"#hassanFaghihiPerson",
    "worksFor": ["#ravisOrganization"],
    ...<lots of other data>...
}
</script>

For this specific one, which consumed by other element i wished i could stop google from detecting this as separate card

<script type="application/ld+json">
{
    "@context": "http://schema.org",
    "@type"       : "Organization",
    "@id"         : "#ravisOrganization",
    ...<lots of other data>...
}
</script>

for example if there was something like:

<script type="application/ld+json">
{
    "@context": "http://schema.org",
    "@type"       : "Organization",
    "@id"         : "#ravisOrganization",
    "Standalone"  : false  <<------------ Is there any such a thing
}
</script>

Answer 1

You can’t control which search result feature a search engine should/shouldn’t show (except for not providing required properties, of course).

You can convey what the primary entity for the particular web page is: by using mainEntity/mainEntityOfPage. This gives consumers the chance to understand what the page is for, and what the secondary entities are (= everything else); but not all consumers make use of it, of course.

If the page is representing a single person, you could use:

{
  "@context": "http://schema.org",
  "@type": "ItemPage",
  "@id": "",
  "mainEntity": {"@id": "#hassanFaghihiPerson"}
}

and/or:

{
  "@context": "http://schema.org",
  "@type": "Person",
  "@id":"#hassanFaghihiPerson",
  "mainEntityOfPage": {"@id": "", "@type": "ItemPage"}
}