Triple
T34208979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Songs for Brandy |
E877596
|
entity |
| Predicate | hasTargetArtist |
P5936
|
FINISHED |
| Object | Brandy Norwood |
—
|
NE NERFINISHED |
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: Brandy Norwood | Statement: [Songs for Brandy, hasTargetArtist, Brandy Norwood]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTargetArtist Context triple: [Songs for Brandy, hasTargetArtist, Brandy Norwood]
-
A.
hasTargetedArtistFullName
Indicates that an entity is associated with the full name of the artist who is the target or subject of a given action or relationship.
-
B.
hasTargetArtistGenre
Indicates that an entity (such as a campaign, recommendation, or product) is aimed at or associated with a specific music artist genre as its intended target.
-
C.
hasArtist
chosen
Indicates that an entity (such as a work or item) is associated with or created by a specific artist.
-
D.
hasArtistRole
Indicates that an entity serves in the capacity or role of an artist in relation to another entity or context.
-
E.
appliesToArtist
Indicates that something (such as a rule, condition, attribute, or action) is relevant or applicable specifically to an artist.
- 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_69f349aff5f0819096275315abea5344 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: May 1, 2026, 1:55 a.m.