Triple

T15034128
Position Surface form Disambiguated ID Type / Status
Subject BBC Radio Theatre E378435 entity
Predicate hasRecordingFacilities P38458 FINISHED
Object true 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: true | Statement: [BBC Radio Theatre, hasRecordingFacilities, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasRecordingFacilities
Context triple: [BBC Radio Theatre, hasRecordingFacilities, true]
  • A. hasMediaFacilities chosen
    Indicates that an entity possesses or provides access to media-related infrastructure or equipment (such as studios, recording, broadcasting, or production facilities).
  • B. hasVideoRecording
    Indicates that there exists an associated video recording capturing or documenting the referenced entity or event.
  • C. hasVideoRecordingAvailableOn
    Indicates that a video recording of something is accessible or hosted on a specified platform, service, or medium.
  • D. hasRecordingContract
    Indicates that an entity is formally bound by an agreement to produce recordings for another entity, typically a record label or similar organization.
  • E. hasVoiceRecorder
    Indicates that one entity possesses or is equipped with a voice recording device or capability in relation to another entity or context.
  • 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_69d85cd46b2c819090d054c27787f677 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7e3a7c8819081f26c2435c1bcb2 completed April 15, 2026, 12:12 a.m.
PD Predicate disambiguation batch_69de9a67cbc481909c19c2de57de4eb7 completed April 14, 2026, 7:50 p.m.
Created at: April 10, 2026, 2:59 a.m.