Triple

T25972540
Position Surface form Disambiguated ID Type / Status
Subject Radio Luxembourg E645843 entity
Predicate broadcastRegime P160309 FINISHED
Object commercial 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: commercial | Statement: [Radio Luxembourg, broadcastRegime, commercial]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: broadcastRegime
Context triple: [Radio Luxembourg, broadcastRegime, commercial]
  • A. broadcastRegion
    Indicates the geographic area or market in which content is transmitted or made available for broadcast.
  • B. broadcastType
    Indicates the specific mode or category of broadcasting used to transmit content (e.g., live, recorded, streaming, or other broadcast formats) between entities.
  • C. broadcastSector
    Indicates that an entity is associated with, operates in, or targets a particular broadcast sector or segment of the broadcasting domain.
  • D. broadcastFacilities
    Indicates that one entity provides or is equipped with the means to transmit or distribute broadcasts (such as radio, television, or digital signals) to an audience.
  • E. broadcastModel
    Indicates that one entity serves as the template or source whose structure or values are replicated and applied across another entity or set of entities.
  • 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_69e77e8768648190b27bb578f14bcb88 completed April 21, 2026, 1:41 p.m.
NER Named-entity recognition batch_69f605055e68819098ab1a9d803ce6a3 completed May 2, 2026, 2:07 p.m.
PD Predicate disambiguation batch_69f5f7fba5248190945acf1561280799 completed May 2, 2026, 1:11 p.m.
PDg Predicate description generation batch_69f600be0de88190989611e952b03117 completed May 2, 2026, 1:48 p.m.
Created at: April 22, 2026, 8:51 a.m.