Triple
T26390508
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Bull TV |
E663397
|
entity |
| Predicate | offersContentGenre |
P131541
|
FINISHED |
| Object | sports programming |
—
|
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: sports programming | Statement: [Red Bull TV, offersContentGenre, sports programming]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offersContentGenre Context triple: [Red Bull TV, offersContentGenre, sports programming]
-
A.
targetGenre
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
B.
servedGenre
chosen
Indicates that a service, venue, or provider offers or specializes in a particular genre (such as a style, category, or type of content).
-
C.
promotesGenre
Indicates that one entity actively supports, advertises, or increases the visibility of a particular genre.
-
D.
supportedGenre
Indicates that an entity (such as a system, service, or tool) is capable of handling, providing, or working with a specified genre.
-
E.
hasTargetGenreCategory
Indicates that something is associated with or classified under a specific target genre category.
- 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_69ee88374adc81909868f3bab374a32f |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f6cee45590819086e489bfccbe4ac3 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
Created at: April 26, 2026, 11:25 p.m.