Triple

T37295002
Position Surface form Disambiguated ID Type / Status
Subject Zain Kapoor E925775 entity
Predicate parentalPrivacyProtection P114942 FINISHED
Object parents avoid excessive media exposure 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: parents avoid excessive media exposure | Statement: [Zain Kapoor, parentalPrivacyProtection, parents avoid excessive media exposure]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: parentalPrivacyProtection
Context triple: [Zain Kapoor, parentalPrivacyProtection, parents avoid excessive media exposure]
  • A. parentProtectsPrivacy chosen
    Indicates that a parent takes actions to safeguard a child’s personal information and privacy.
  • B. parentStudio
    Indicates that one studio serves as the parent or owning studio of another studio.
  • C. familyControlled
    Indicates that an entity is owned or effectively governed by one or more members of the same family, who hold decisive control over its decisions or operations.
  • D. hasParentalControlType
    Indicates the specific type or category of parental control applied to an entity (such as content, a device, or a user account).
  • E. parentalCare
    Indicates that one entity provides nurturing, protection, or support to another in a parent-like role.
  • 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_69f76eb0f86c819098dee07393e69ec3 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69fe6c811bcc81908b1e1b1f8bcb071b completed May 8, 2026, 11:06 p.m.
PD Predicate disambiguation batch_69fe6c026d5481908b7a814dcf38c183 completed May 8, 2026, 11:04 p.m.
Created at: May 3, 2026, 4:16 p.m.