Triple

T37677791
Position Surface form Disambiguated ID Type / Status
Subject Osbourne family E938142 entity
Predicate hasMediaReputationFor P93104 FINISHED
Object dysfunctional family dynamics 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: dysfunctional family dynamics | Statement: [Osbourne family, hasMediaReputationFor, dysfunctional family dynamics]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMediaReputationFor
Context triple: [Osbourne family, hasMediaReputationFor, dysfunctional family dynamics]
  • A. providesReputationWith
    Indicates that one entity grants or assigns a reputation value, score, or status to another entity.
  • B. hasPolicyReputationFor
    Indicates that an entity is recognized or regarded in a particular way with respect to its policies or policy-related behavior.
  • C. haveReputation chosen
    Indicates that an entity is recognized or regarded in a certain way by others, reflecting its perceived character, quality, or status.
  • D. hasViewReputation
    Indicates that an entity holds a reputation or recognized standing specifically related to viewing, observing, or accessing something.
  • E. hasReputationAmong
    Indicates that an entity is regarded or perceived in a particular way by a specified group or audience.
  • 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_69f76ed7b1408190ba8c93c53cb8becf completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_69ffa9677be08190852c8ef6c2545fed completed May 9, 2026, 9:38 p.m.
PD Predicate disambiguation batch_69ffa6570e2c8190a9d7b37f12b91d9a completed May 9, 2026, 9:25 p.m.
Created at: May 3, 2026, 4:18 p.m.