Triple
T15178262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bed |
E362668
|
entity |
| Predicate | labelMarketingFocus |
P117019
|
FINISHED |
| Object | urban contemporary radio |
—
|
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: urban contemporary radio | Statement: [Bed, labelMarketingFocus, urban contemporary radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: labelMarketingFocus Context triple: [Bed, labelMarketingFocus, urban contemporary radio]
-
A.
labelMarketingPositioning
Indicates that an entity defines or assigns the marketing positioning (how something is presented or positioned in the market) for another entity.
-
B.
labelMarketingConcept
Indicates that something is designated or identified as a specific marketing concept.
-
C.
brandFocus
Indicates that a brand primarily concentrates its efforts, messaging, or resources on a particular target, theme, or market segment.
-
D.
categoryFocus
Indicates that one entity is the primary subject, theme, or focal point within the broader category defined by the other entity.
-
E.
labelCatalog
Indicates assigning or associating a descriptive label or identifier with a catalog entity or catalog entry.
- 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_69d85a09a39c81908759f23268e2d408 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00663b4148190b647592eda315d1d |
completed | April 15, 2026, 9:42 p.m. |
| PD | Predicate disambiguation | batch_69deb97bd8bc8190b2ad4888f97cf963 |
completed | April 14, 2026, 10:02 p.m. |
| PDg | Predicate description generation | batch_69dec72059c08190a34f513a00185b08 |
completed | April 14, 2026, 11 p.m. |
Created at: April 10, 2026, 3:09 a.m.