Triple

T35700367
Position Surface form Disambiguated ID Type / Status
Subject Peacock Foundation E1031562 entity
Predicate hasSuccessorNameUsedBy P201382 FINISHED
Object Peacock Foundation Studio NE NERFINISHED

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: Peacock Foundation Studio | Statement: [Peacock Foundation, hasSuccessorNameUsedBy, Peacock Foundation Studio]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasSuccessorNameUsedBy
Context triple: [Peacock Foundation, hasSuccessorNameUsedBy, Peacock Foundation Studio]
  • A. hasSuccessorNames
    Indicates that an entity is followed or replaced by one or more entities identified as its successors.
  • B. hasSuccessorUse
    Indicates that one use or application of something is directly followed or replaced by another use in a sequence or progression.
  • C. successorUsedIn
    Indicates that a successor entity is utilized or referenced within the context, operation, or implementation of another entity.
  • D. hasSuccessorNameConflict
    Indicates that an entity’s successor has a name that conflicts (e.g., duplicates or clashes) with another existing or expected name in the system.
  • E. hasSuccessors
    Indicates that an entity is followed or replaced by one or more subsequent entities in a sequence, process, or lineage.
  • 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_69f76e0d393c8190b6303c64408736db completed May 3, 2026, 3:47 p.m.
NER Named-entity recognition batch_69ffef812da48190b875a7376b24f92d completed May 10, 2026, 2:37 a.m.
PD Predicate disambiguation batch_69ffedecd580819097851b1473fdd6ed completed May 10, 2026, 2:31 a.m.
PDg Predicate description generation batch_69ffef8003c081909ec2413b4ea08d43 completed May 10, 2026, 2:37 a.m.
Created at: May 3, 2026, 4:05 p.m.