Triple

T6524592
Position Surface form Disambiguated ID Type / Status
Subject Workplace from Meta E151269 entity
Predicate dataSegregation P71408 FINISHED
Object separate from consumer Facebook accounts LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: separate from consumer Facebook accounts | Statement: [Workplace from Meta, dataSegregation, separate from consumer Facebook accounts]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dataSegregation
Context triple: [Workplace from Meta, dataSegregation, separate from consumer Facebook accounts]
  • A. dataPolicy
    Indicates that one entity defines or governs how data related to another entity is collected, used, stored, or shared.
  • B. securityClassification
    Indicates the level or category of security sensitivity or access restriction assigned to an entity.
  • C. dataSubject
    Indicates that one entity is the individual to whom the personal data or information in question relates.
  • D. confidentialityProtectedBy
    Indicates that the confidentiality of some information is safeguarded or ensured by a specified protection mechanism, policy, or entity.
  • E. hasDataProtectionAuthority
    Indicates that an entity is subject to, overseen by, or associated with a specific data protection authority responsible for regulating its handling of personal data.
  • F. None of above. chosen

Provenance (4 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69c687f522748190b3058405553cdabd completed March 27, 2026, 1:36 p.m.
NER Named-entity recognition batch_69c6ad9831f88190a2b64cf6bc8c9a11 completed March 27, 2026, 4:17 p.m.
PD Predicate disambiguation batch_69c68abbc7148190a8270d47fe10cc31 completed March 27, 2026, 1:48 p.m.
PDg Predicate description generation batch_69c69f362ee4819090e8fa48caef7d7d completed March 27, 2026, 3:16 p.m.
Created at: March 27, 2026, 1:45 p.m.