Triple

T28204387
Position Surface form Disambiguated ID Type / Status
Subject Radio Rock crew E716972 entity
Predicate broadcastTargetAudience P10804 FINISHED
Object UK listeners 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: UK listeners | Statement: [Radio Rock crew, broadcastTargetAudience, UK listeners]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: broadcastTargetAudience
Context triple: [Radio Rock crew, broadcastTargetAudience, UK listeners]
  • A. broadcastType
    Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
  • B. broadcastPotential
    Indicates that an entity has the capability or suitability to be broadcast or transmitted to an audience or network.
  • C. broaderTarget
    Indicates that one target concept encompasses or is more general than another, defining a broader-to-narrower target relationship.
  • D. typicalAudience chosen
    Indicates the group of people for whom something (such as a work, product, or resource) is primarily intended or most suitable.
  • E. broadcastImpact
    Indicates the effect or influence that a broadcast (such as a message, signal, or transmission) has on its intended audience or environment.
  • 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_69efd6b826908190857e6e7dad74ed93 completed April 27, 2026, 9:35 p.m.
NER Named-entity recognition batch_69f6617ba4a88190bfc5c305acb4f93f completed May 2, 2026, 8:41 p.m.
PD Predicate disambiguation batch_69f660f082508190a95a7888ad66cb2e completed May 2, 2026, 8:39 p.m.
Created at: April 27, 2026, 10:34 p.m.