Triple

T4051927
Position Surface form Disambiguated ID Type / Status
Subject CCPA E84603 entity
Predicate allowsPrivateRightOfAction P21381 FINISHED
Object yes, for certain data breaches 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: yes, for certain data breaches | Statement: [CCPA, allowsPrivateRightOfAction, yes, for certain data breaches]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: allowsPrivateRightOfAction
Context triple: [CCPA, allowsPrivateRightOfAction, yes, for certain data breaches]
  • A. canOwn
    Indicates that one entity is permitted or legally able to possess or hold ownership rights over another entity.
  • B. canTakeActionWith
    Indicates that one entity is able or permitted to perform an action jointly or in coordination with another entity.
  • C. allows
    Indicates that one entity grants permission, capability, or opportunity for another entity to perform an action or be in a certain state.
  • D. hasLegalRight chosen
    Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
  • E. restrictedRight
    Indicates that an entity’s ability to exercise a particular right is limited, constrained, or subject to specific conditions or prohibitions.
  • F. None of above.

Provenance (3 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_69aed933bec881909edfa28ebb69c634 completed March 9, 2026, 2:29 p.m.
NER Named-entity recognition batch_69aefb8539148190990468c1429be9dd completed March 9, 2026, 4:55 p.m.
PD Predicate disambiguation batch_69aef90249e4819095e9e043bc4aa9a6 completed March 9, 2026, 4:44 p.m.
Created at: March 9, 2026, 3:37 p.m.