Triple
T526317
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | France Télévisions |
E10925
|
entity |
| Predicate | broadcastsContentType |
P15169
|
FINISHED |
| Object | news |
—
|
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: news | Statement: [France Télévisions, broadcastsContentType, news]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastsContentType Context triple: [France Télévisions, broadcastsContentType, news]
-
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.
broadcasterType
Indicates the category or kind of broadcaster involved in the relationship or action (e.g., public, commercial, online).
-
C.
mediaType
Indicates the format or category of media associated with an entity, such as text, image, audio, or video.
-
D.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
E.
broadcastProgram
Indicates that a media outlet or channel transmits a specific program to an audience via a broadcast medium.
- 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.