Triple
T26379932
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Crenshaw (mixtape) |
E660996
|
entity |
| Predicate | marketingCampaignName |
P48078
|
FINISHED |
| Object | Proud2Pay |
—
|
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: Proud2Pay | Statement: [Crenshaw (mixtape), marketingCampaignName, Proud2Pay]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marketingCampaignName Context triple: [Crenshaw (mixtape), marketingCampaignName, Proud2Pay]
-
A.
hasCampaignName
chosen
Indicates that an entity is associated with a specific campaign identified by a particular name.
-
B.
promotionalCampaign
Indicates a relationship where one entity organizes or runs a coordinated set of marketing activities aimed at promoting another entity, product, or service.
-
C.
marketingNameOf
Indicates that one entity is the marketing or brand name used to promote or refer to another entity.
-
D.
testCampaign
Indicates that an entity is involved in or associated with a campaign conducted for testing, experimentation, or evaluation purposes.
-
E.
launchCampaign
Indicates initiating and putting into operation a planned promotional or marketing campaign.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6352fdb788190b9bad30243690743 |
completed | May 2, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69f631850ae08190a0ba51e4f1e4ccb3 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 26, 2026, 11:03 p.m.