Triple
T14106350
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TF1 Publicité |
E339513
|
entity |
| Predicate | regulatesContentType |
P110926
|
FINISHED |
| Object | commercial advertising messages |
—
|
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 advertising messages | Statement: [TF1 Publicité, regulatesContentType, commercial advertising messages]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatesContentType Context triple: [TF1 Publicité, regulatesContentType, commercial advertising messages]
-
A.
addsContentType
Indicates that one entity augments or associates another entity with a specific content type.
-
B.
regulatesContentFor
Indicates that one entity controls, manages, or sets rules governing the content produced, shared, or accessed by another entity.
-
C.
hasContentType
Indicates that an entity is associated with or classified by a specific type of content.
-
D.
regulatesContentBy
chosen
Indicates that one entity controls, directs, or sets rules for the nature, form, or distribution of another entity’s content.
-
E.
describesContentType
Indicates that one entity specifies or characterizes the type or category of content associated with another entity.
- 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_69d81c69b5c8819094aa1abf18302908 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600ada808190b92d67dc30f13d15 |
completed | April 14, 2026, 3:40 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.