Triple
T23371583
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Somebody for Me |
E593487
|
entity |
| Predicate | intendedForMarket |
P55993
|
FINISHED |
| Object | mainstream urban 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: mainstream urban radio | Statement: [Somebody for Me, intendedForMarket, mainstream urban radio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedForMarket Context triple: [Somebody for Me, intendedForMarket, mainstream urban radio]
-
A.
producedForMarket
Indicates that something has been created or manufactured with the intention of being sold or traded in a market.
-
B.
marketedFor
Indicates that something is promoted, advertised, or positioned as being intended or suitable for a particular use, audience, or purpose.
-
C.
marketedWith
Indicates that two or more products or services are promoted together as part of the same marketing effort or campaign.
-
D.
destinedFor
Indicates that one entity is intended, assigned, or meant to be used for, received by, or directed toward another entity or purpose.
-
E.
hasMarketingTarget
chosen
Indicates that an entity is aimed at or intended to appeal to a specific marketing audience or segment.
- 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_69e25d2593c88190bcdf4a716a94ccb2 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3af45ec8190a32aa4e5f04f6756 |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:32 p.m.