Triple
T33090553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Go Red for Women |
E846767
|
entity |
| Predicate | hasCampaignElement |
P85034
|
FINISHED |
| Object | National Wear Red Day |
—
|
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: National Wear Red Day | Statement: [Go Red for Women, hasCampaignElement, National Wear Red Day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCampaignElement Context triple: [Go Red for Women, hasCampaignElement, National Wear Red Day]
-
A.
hasCampaignStructure
Indicates that one entity possesses, defines, or is associated with a particular organizational or strategic campaign framework of another entity.
-
B.
hasCampaignName
Indicates that an entity is associated with a specific campaign identified by a particular name.
-
C.
hasMarketingCampaign
Indicates that an entity is associated with or utilizes a specific marketing campaign.
-
D.
hasMarketingElement
chosen
Indicates that one entity includes, is associated with, or makes use of a particular marketing-related component or feature.
-
E.
hasKeyCampaignTactic
Indicates that an entity employs or is associated with a primary or strategically important campaign tactic.
- 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_69f3495590dc8190aa04f3dec74ce976 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff14d596e88190be5263b7f96a96cd |
completed | May 9, 2026, 11:04 a.m. |
| PD | Predicate disambiguation | batch_69ff13f0208081909369aeb3b77a6b1f |
completed | May 9, 2026, 11:01 a.m. |
Created at: May 1, 2026, 1:26 a.m.