Triple

T526339
Position Surface form Disambiguated ID Type / Status
Subject France Télévisions E10925 entity
Predicate broadcastStandard P15170 FINISHED
Object digital terrestrial television 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: digital terrestrial television | Statement: [France Télévisions, broadcastStandard, digital terrestrial television]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: broadcastStandard
Context triple: [France Télévisions, broadcastStandard, digital terrestrial television]
  • 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. broadcastRole
    Indicates that an entity has a specific role or function within a broadcast or transmission context.
  • C. broadcastProgram
    Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
  • D. broadcastNetwork
    Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
  • E. broadcastRegion
    Indicates the geographic area or market in which content is transmitted or made available for broadcast.
  • 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_69a2e84b16c4819088d284c47c3a7968 completed Feb. 28, 2026, 1:06 p.m.
NER Named-entity recognition batch_69a2f1d0d22081908aad915482d39e74 completed Feb. 28, 2026, 1:46 p.m.
PD Predicate disambiguation batch_69a2f0198ecc8190883849e5a8245963 completed Feb. 28, 2026, 1:39 p.m.
PDg Predicate description generation batch_69a2f0dcff1881909c18e8c599c150a1 completed Feb. 28, 2026, 1:42 p.m.
Created at: Feb. 28, 2026, 1:12 p.m.